nodejs / nodejs/reliability

CI Reliability 2024-10-08

Open
#990 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
57
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Failures in node-test-pull-request/62882 to node-test-pull-request/62980 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-10-08.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2024-10-08 00:09 0 17 17 3 63 17.53%

Open https://github.com/nodejs/reliability/blob/main/reports/2024-10-08.md to see failure details

Progress
  • sequential/test-http-server-request-timeouts-mixed (8)
  • es-module/test-loaders-workers-spawned (7)
  • node-api/test_threadsafe_function/test (6)
  • parallel/test-stream-readable-unpipe-resume (6)
  • parallel/test-net-write-fully-async-buffer (4)
  • parallel/test-async-context-frame (3)
  • wpt/test-compression (3)
  • parallel/test-performance-eventlooputil (2)
  • pummel/test-hash-seed (2)
  • pummel/test-heapdump-shadow-realm (2)
  • ERROR: Error fetching remote repo 'origin' (4)
  • Error: invalid syntax (13)
  • fatal: No rebase in progress? (5)
  • fatal error: Killed signal terminated program cc1plus (4)
  • Failed to trigger sub builds (2)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading reports/2024-10-08.md and the linked CI runs, using the listed test names and error messages to identify the recurring failures. The issue is complete when the reported failures have been investigated and the corresponding progress entries are resolved or updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, shell
Domain
ci-cd, devops, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.