nodejs / nodejs/reliability

CI Reliability 2026-02-23

Open
#1,468 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/71309 to node-test-pull-request/71396 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-02-23.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-02-23 00:15 7 17 23 7 46 19.77%

Open https://github.com/nodejs/reliability/blob/main/reports/2026-02-23.md to see failure details

Progress
  • Unexpected termination of the channel (3)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • Failed to create a temp file on /home/iojs/build/workspace/node (2)
  • fatal: No rebase in progress? (3)
  • ERROR: Error fetching remote repo 'origin' (4)
  • wpt/test-hr-time (5)
  • sequential/test-performance-eventloopdelay (3)
  • test-runner/test-run-watch-emit-restarted (3)
  • benchmark/test-benchmark-esm (2)
  • client-proxy/test-https-proxy-request-invalid-char-in-url (2)
  • parallel/test-child-process-fork-closed-channel-segfault (2)
  • parallel/test-child-process-fork-exec-path (2)
  • parallel/test-file-write-stream4 (2)
  • parallel/test-http-client-response-domain (2)
  • parallel/test-module-loading-globalpaths (2)
  • parallel/test-promise-reject-callback-exception (2)
  • parallel/test-runner-run-watch (2)
  • parallel/test-runner-watch-mode (2)
  • parallel/test-strace-openat-openssl (2)
  • parallel/test-vm-sigint (2)
  • test-runner/test-run-watch-without-file (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 with reports/2026-02-23.md and the linked node-test-pull-request jobs, using the listed failure names to group the affected cases. Review the generated output from ncu-ci walk pr --stats=true --markdown reports/2026-02-23.md; done means the listed CI failures have been addressed and the corresponding progress items can be checked.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, shell
Domain
ci-cd, devops
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.