CI Reliability 2026-09-12
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/77272 to node-test-pull-request/77365 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-09-12.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-09-12 00:15 | 17 | 7 | 15 | 27 | 34 | 12.50% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-09-12.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(4) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(7) -
Error: [WinError 5] Access is denied: 'C:\\Users\\Administrator\\clcache\\stats.txt.new' -> 'C:\\Users\\Administrator\\clcache\\stats.txt'(5) -
FATAL: Channel "hudson.remoting.Channel@60179e73:JNLP4-connect connection from ... Remote call on JNLP4-connect connection from 8.225.232.44/8.225.232.44:55632 failed. The channel is closing down or has closed down(5) -
fatal: No rebase in progress?(5) -
FATAL: java.nio.channels.ClosedChannelException(3) -
Unexpected token '<', ..."(2) -
parallel/test-http2-close-while-writing(5) -
parallel/test-runner-watch-mode(5) -
parallel/test-external-memory-reasonable-size(2) -
sequential/test-performance-eventloopdelay(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 the linked node-test-pull-request builds and the 2026-09-12 report, then inspect the failure details for each listed error and test failure. Group the recurring failures by cause and verify fixes against the affected CI jobs; done means the reported recurring failures no longer occur and the reliability report is green.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100