CI Reliability 2026-07-18
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/74777 to node-test-pull-request/74868 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-07-18.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-07-18 00:24 | 10 | 18 | 15 | 2 | 55 | 20.45% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-07-18.md to see failure details
Progress
-
fatal: No rebase in progress?(10) -
error: could not apply 61890720c8a... add readme and initial code(7) -
sh: line 12: [: -gt: unary operator expected(5) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2) -
parallel/test-process-finalization(11) -
sequential/test-debugger-pid(8) -
parallel/test-debugger-probe-failure-process-exit(4) -
sea/test-single-executable-application(4) -
parallel/test-npm-install(2) -
parallel/test-runner-run-watch(2) -
parallel/test-sqlite-backup(2) -
sequential/test-performance-eventloopdelay(2) -
sequential/test-watch-mode-restart-esm-loading-error(2) -
test-runner/test-run-watch-cwd-isolation-none-argv(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-07-18.md and inspect the linked CI runs for the listed failures. Reproduce the affected jobs or tests, including the rebase, debugger, test-runner, SEA, SQLite, and watch-mode entries, then resolve the recurring failures and update the progress checklist when those failures no longer recur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100