CI Reliability 2026-04-10
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/72498 to node-test-pull-request/72592 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-10.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-10 00:19 | 12 | 15 | 13 | 6 | 54 | 18.29% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-10.md to see failure details
Progress
-
Unexpected termination of the channel(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
fatal: No rebase in progress?(2) -
sh: line 12: [: -gt: unary operator expected(2) -
wpt/test-wasm-jsapi(5) -
parallel/test-inspector-dom-storage(4) -
sequential/test-debugger-pid(4) -
client-proxy/test-https-proxy-request-invalid-char-in-url(3) -
parallel/test-runner-output(3) -
parallel/test-worker-nearheaplimit-deadlock(2) -
test-runner/test-run-watch-run-duration(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-04-10.md and the linked node-test-pull-request jobs, then compare the failure details with the unchecked Progress entries. Reproduce the recurring failures and use the checklist to track which reported CI problems have been resolved.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100