CI Reliability 2026-01-28
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/70987 to node-test-pull-request/71082 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-28 00:13 | 1 | 16 | 13 | 6 | 64 | 17.20% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-28.md to see failure details
Progress
-
parallel/test-repl-programmatic-history(18) -
parallel/test-inspector-network-http2-compressed(11) -
sequential/test-single-executable-application-empty(6) -
sequential/test-watch-mode-restart-esm-loading-error(4) -
es-module/test-vm-contextified-script-leak(3) -
sequential/test-performance-eventloopdelay(3) -
test-runner/test-run-watch-dependency-repeatedly(3) -
test-runner/test-run-watch-emit-restarted(3) -
async-hooks/test-emit-before-on-destroyed(2) -
parallel/test-domain-multi(2) -
test-runner/test-run-watch-repeatedly(2) -
test-runner/test-run-watch-run-duration(2) -
test-runner/test-run-watch-without-file(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) -
fatal error: too many errors emitted, stopping now [-ferror-limit=](2) -
fatal: no rebase in progress(2)
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-01-28.md and the linked node-test-pull-request jobs, then inspect the listed failures such as parallel/test-repl-programmatic-history and test-runner watch tests. The issue is complete when the reported recurring CI failures are investigated and the corresponding entries are resolved or otherwise explained.
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
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100