CI Reliability 2026-01-29
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/71011 to node-test-pull-request/71106 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-29.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-29 00:14 | 1 | 15 | 17 | 4 | 63 | 15.79% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-29.md to see failure details
Progress
-
parallel/test-repl-programmatic-history(16) -
parallel/test-inspector-network-http2-compressed(6) -
sequential/test-single-executable-application-empty(6) -
sequential/test-watch-mode-restart-esm-loading-error(5) -
es-module/test-vm-contextified-script-leak(3) -
parallel/test-runner-output(3) -
test-runner/test-run-watch-dependency-repeatedly(3) -
test-runner/test-run-watch-repeatedly(3) -
test-runner/test-run-watch-run-duration(3) -
test-runner/test-run-watch-without-file(3) -
wpt/test-hr-time(3) -
async-hooks/test-emit-before-on-destroyed(2) -
parallel/test-domain-multi(2) -
parallel/test-http2-close-while-writing(2) -
sequential/test-performance-eventloopdelay(2) -
test-runner/test-run-watch-emit-restarted(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) -
Failed to trigger node-test-commit(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(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-29.md and the linked node-test-pull-request jobs, then inspect the listed failing tests and CI errors. Use the Progress checklist to track investigation across the failures; done means the identified failures and infrastructure errors have been addressed and the CI jobs return to a reliable green state.
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
- 25/100