CI Reliability 2026-04-08
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/72450 to node-test-pull-request/72541 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-08.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-08 00:21 | 5 | 18 | 7 | 2 | 68 | 19.35% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-08.md to see failure details
Progress
-
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(4) -
sh: line 12: [: -gt: unary operator expected(4) -
ERROR: out of memory(2) -
error: remote GitHub already exists.(2) -
sequential/test-debugger-pid(5) -
parallel/test-inspector-dom-storage(4) -
wpt/test-wasm-jsapi(4) -
parallel/test-debugger-heap-profiler(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-08.md and the linked node-test-pull-request runs 72450 through 72541. Use the listed ncu-ci walk command and inspect the failure details for the recurring JUnit, shell, memory, GitHub, and test failures. Done means the identified failures are addressed and the affected CI runs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, 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