CI Reliability 2026-01-06
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/70588 to node-test-pull-request/70685 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-06.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-06 00:12 | 0 | 8 | 28 | 16 | 48 | 9.52% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-06.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(5) -
fatal error: too many errors emitted, stopping now [-ferror-limit=](5) -
Failed to trigger node-test-commit(4) -
fatal error: Killed signal terminated program cc1plus(4) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(2) -
parallel/test-repl-programmatic-history(8) -
parallel/test-zlib-brotli-16GB(4) -
parallel/test-quic-test-client(3) -
sequential/test-performance-eventloopdelay(3) -
test-runner/test-run-watch-run-duration(3) -
client-proxy/test-https-proxy-request(2) -
client-proxy/test-https-proxy-request-connection-refused(2) -
es-module/test-vm-contextified-script-leak(2) -
node-api/test_threadsafe_function/test(2) -
parallel/test-blob(2) -
wpt/test-wasm-webapi(2) -
wpt/test-webcrypto(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-06.md and the linked node-test-pull-request builds from 70588 through 70685. Review the listed failure categories and test names, then use the ncu-ci walk pr command context to trace each recurring failure. Done means the reported CI failures are addressed and the progress checklist is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, 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