nodejs / nodejs/reliability

CI Reliability 2026-02-09

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-02-09 00:16 1 19 35 4 41 20.00%

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

Progress
  • parallel/test-repl-programmatic-history (5)
  • sequential/test-watch-mode-restart-esm-loading-error (5)
  • parallel/test-http2-close-while-writing (4)
  • sequential/test-performance-eventloopdelay (3)
  • sequential/test-single-executable-application-empty (3)
  • wpt/test-hr-time (3)
  • async-hooks/test-emit-before-on-destroyed (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-node-output-sourcemaps (2)
  • parallel/test-promise-reject-callback-exception (2)
  • parallel/test-runner-output (2)
  • parallel/test-runner-watch-mode (2)
  • parallel/test-zlib-brotli-16GB (2)
  • 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? (4)
  • Failed to trigger sub builds (3)

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-09.md and the linked node-test-pull-request builds from 71162 through 71260 to review the failure details. Investigate the listed test and infrastructure failures, then verify that the affected CI jobs no longer reproduce them; completion is not defined beyond resolving the reported failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, shell
Domain
ci-cd, infrastructure, 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.