CI Reliability 2026-07-04
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/74438 to node-test-pull-request/74536 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-07-04.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-07-04 00:29 | 0 | 21 | 10 | 3 | 66 | 21.65% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-07-04.md to see failure details
Progress
-
parallel/test-npm-install(18) -
parallel/test-path-win32-normalize-device-names(10) -
parallel/test-debugger-probe-failure-process-exit(7) -
sea/test-single-executable-application(6) -
test-runner/test-run-watch-cwd-isolation-none-argv(6) -
parallel/test-runner-cli(4) -
parallel/test-runner-flag-propagation(4) -
parallel/test-runner-global-setup-teardown(4) -
sea/test-single-executable-application-empty(4) -
parallel/test-debugger-probe-expression-throws(3) -
parallel/test-esm-loader-hooks-inspect-wait(3) -
sequential/test-watch-mode-restart-esm-loading-error(3) -
es-module/test-require-module-tla-print-execution(2) -
parallel/test-debugger-probe-bound-never-hit(2) -
parallel/test-debugger-probe-max-hit-partial(2) -
parallel/test-runner-cli-randomize(2) -
pummel/test-timers(2) -
sequential/test-watch-mode-worker(2) -
wasi/test-wasi-pthread(2) -
ERROR: Error fetching remote repo 'origin'(7) -
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: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(3) -
Failed to trigger node-test-commit(3) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(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
Open reports/2026-07-04.md and inspect the linked node-test-pull-request jobs for failure details. Use the Progress list to investigate the repeated test and CI infrastructure failures, then verify that the affected checks no longer fail across pull requests.
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
- Needs clarification
- Newbie friendliness
- 35/100