nodejs / nodejs/reliability

CI Reliability 2026-02-21

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-02-21 00:15 0 19 24 3 54 19.59%

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

Progress
  • Failed to create a temp file on /home/iojs/build/workspace/node (4)
  • Unexpected termination of the channel (3)
  • Build timed out (after 60 minutes). Marking the build as failed. (2)
  • fatal: No rebase in progress? (5)
  • ERROR: Error fetching remote repo 'origin' (4)
  • wpt/test-hr-time (5)
  • test-runner/test-run-watch-without-file (4)
  • 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-vm-sigint (2)
  • sequential/test-performance-eventloopdelay (2)
  • sequential/test-watch-mode-restart-esm-loading-error (2)
  • test-runner/test-run-watch-dependency-repeatedly (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 the linked reports/2026-02-21.md report and the CI runs from node-test-pull-request/71288 through 71382. Use the listed failure messages and test names to group failures before investigating them. Done means the recurring failures in the Progress list have been diagnosed and addressed, with the affected CI jobs returning reliably.

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
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.