CI Reliability 2026-07-23
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/74932 to node-test-pull-request/75029 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-07-23.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-07-23 00:26 | 4 | 12 | 11 | 13 | 60 | 14.46% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-07-23.md to see failure details
Progress
-
Unexpected termination of the channel(3) -
ERROR: Error fetching remote repo 'origin'(10) -
error: could not apply 61890720c8a... add readme and initial code(8) -
fatal: No rebase in progress?(7) -
Failed to trigger node-test-commit(6) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(3) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(2) -
parallel/test-repl-user-error-handler(13) -
parallel/test-http2-socket-proxy-destroy(5) -
sequential/test-performance-eventloopdelay(4) -
test-runner/test-run-watch-cwd-isolation-none(4) -
parallel/test-debugger-probe-failure-hang-during-evaluate(3)
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-07-23.md and the linked node-test-pull-request jobs covering builds 74932 through 75029. Review the listed failure categories and affected tests, then trace each failure to its relevant CI or test entry point. Done means the assigned failures are resolved or explained and the corresponding Progress checklist is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100