CI Reliability 2026-02-02
Open
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/71059 to node-test-pull-request/71158 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-02-02.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-02-02 00:15 | 0 | 22 | 16 | 6 | 56 | 23.40% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-02-02.md to see failure details
Progress
-
parallel/test-repl-programmatic-history(12) -
sequential/test-watch-mode-restart-esm-loading-error(6) -
parallel/test-child-process-fork-exec-path(3) -
parallel/test-file-write-stream4(3) -
parallel/test-module-loading-globalpaths(3) -
parallel/test-runner-output(3) -
sequential/test-single-executable-application-empty(3) -
test-runner/test-run-watch-dependency-repeatedly(3) -
test-runner/test-run-watch-run-duration(3) -
test-runner/test-run-watch-without-file(3) -
wpt/test-hr-time(3) -
parallel/test-http2-close-while-writing(2) -
parallel/test-repl-history-navigation(2) -
parallel/test-repl-load-multiline-from-history(2) -
parallel/test-repl-multiline-navigation(2) -
parallel/test-repl-multiline-navigation-while-adding(2) -
parallel/test-repl-null(2) -
parallel/test-repl-options(2) -
parallel/test-repl-persistent-history(2) -
parallel/test-runner-run(2) -
sequential/test-performance-eventloopdelay(2) -
test-runner/test-run-watch-emit-restarted(2) -
test-runner/test-run-watch-esm-dependency(2) -
test-runner/test-run-watch-repeatedly(2) -
wpt/test-streams(2) -
wpt/test-wasm-webapi(2) -
warning: failed to remove tools/doc/node_modules/highlight.js/styles/base16: Directory not empty(3) -
fatal: No rebase in progress?(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
Failed to trigger node-test-commit(2) -
Unexpected token '<', "(4)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with reports/2026-02-02.md and the linked node-test-pull-request runs to inspect the failure details. Use the unchecked test names and CI errors as entry points; done means the recurring failures are addressed and the Progress checklist is complete.
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
- 35/100