nodejs / nodejs/reliability

CI Reliability 2026-02-11

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

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2026-02-11 00:20 1 20 29 3 47 20.83%

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

Progress
  • parallel/test-http2-close-while-writing (4)
  • test-runner/test-run-watch-without-file (4)
  • sequential/test-single-executable-application-empty (3)
  • sequential/test-watch-mode-restart-esm-loading-error (3)
  • wpt/test-hr-time (3)
  • async-hooks/test-emit-before-on-destroyed (2)
  • parallel/test-runner-output (2)
  • parallel/test-runner-watch-mode (2)
  • parallel/test-zlib-brotli-16GB (2)
  • sequential/test-performance-eventloopdelay (2)
  • test-runner/test-run-watch-run-duration (2)
  • Failed to create a temp file on /home/iojs/build/workspace/node (4)
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
  • Unexpected token '<', " (8)

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-11.md and the linked node-test-pull-request jobs to inspect the failure details behind the listed checks. Trace each named test or CI error to its relevant repository context, then verify that the affected failures no longer recur in CI and that the progress list can be updated.

Written by the indexing model from the issue text.

Assessment

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