CI Reliability 2026-09-02
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/76767 to node-test-pull-request/76834 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-09-02.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-09-02 00:17 | 27 | 8 | 4 | 21 | 40 | 15.38% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-09-02.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(4) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(2) -
FATAL: Channel "hudson.remoting.Channel@78887484:JNLP4-connect connection from ... Remote call on JNLP4-connect connection from 67.158.54.159/67.158.54.159:35935 failed. The channel is closing down or has closed down(7) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(6) -
Failed to trigger node-test-commit(5) -
FATAL: java.nio.channels.ClosedChannelException(3) -
Failed to trigger fanned build(3) -
parallel/test-fs-watch-recursive-delete-race(14) -
parallel/test-http2-bidirectional-write-deadlock(6) -
parallel/test-fs-watch-enoent(4) -
client-proxy/test-https-proxy-request-invalid-char-in-url(3) -
parallel/test-buffer-tostring-rangeerror(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-09-02.md and the linked node-test-pull-request builds, then review how ncu-ci walk pr --stats=true --markdown reports/2026-09-02.md groups failures. Trace the listed infrastructure and test failures to their logs and relevant CI configuration or tests. The issue does not define a completion criterion beyond resolving the recurring failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100