CI Reliability 2026-04-09
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/72470 to node-test-pull-request/72563 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-09.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-09 00:16 | 6 | 15 | 14 | 6 | 59 | 17.05% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-09.md to see failure details
Progress
-
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
sh: line 12: [: -gt: unary operator expected(3) -
sequential/test-debugger-pid(5) -
parallel/test-inspector-dom-storage(4) -
wpt/test-wasm-jsapi(4) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
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-09.md and the linked node-test-pull-request jobs to inspect the failure details. Investigate the listed JUnit-report, shell, debugger, inspector, WebAssembly, and proxy test failures, then verify that the affected CI failures are resolved and the relevant PRs pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100