CI Reliability 2026-01-07
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/70592 to node-test-pull-request/70691 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-07.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-07 00:11 | 0 | 9 | 26 | 15 | 50 | 10.59% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-07.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) -
node-api/test_threadsafe_function/test(3) -
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) -
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-07.md and the linked node-test-pull-request runs to review the failure details. The report was generated with ncu-ci walk pr --stats=true --markdown, and completion means investigating the listed recurring failures and updating the Progress checklist with the resulting status.
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