nodejs / nodejs/reliability

CI Reliability 2026-02-12

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-02-12 00:15 2 16 30 3 49 16.84%

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

Progress
  • sequential/test-performance-eventloopdelay (5)
  • test-runner/test-run-watch-without-file (5)
  • sequential/test-watch-mode-restart-esm-loading-error (3)
  • wpt/test-hr-time (3)
  • 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-zlib-brotli-16GB (2)
  • test-runner/test-run-watch-run-duration (2)
  • Failed to create a temp file on /home/iojs/build/workspace/node (6)
  • Unexpected termination of the channel (2)
  • fatal: No rebase in progress? (6)

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-12.md and the linked node-test-pull-request builds, then inspect the listed failing tests and CI errors. Use the affected test names and ncu-ci walk output to trace each repeated failure. Done means the checklist items are resolved and the impacted CI runs return green.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.