CI Reliability 2026-07-02
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/74400 to node-test-pull-request/74499 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-07-02.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-07-02 00:36 | 0 | 14 | 24 | 4 | 58 | 14.58% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-07-02.md to see failure details
Progress
-
parallel/test-npm-install(12) -
parallel/test-path-win32-normalize-device-names(11) -
sea/test-single-executable-application-empty(6) -
parallel/test-debugger-probe-failure-process-exit(4) -
parallel/test-runner-cli(4) -
parallel/test-runner-flag-propagation(4) -
parallel/test-runner-global-setup-teardown(4) -
sea/test-single-executable-application(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) -
test-runner/test-run-watch-cwd-isolation-none-argv(3) -
parallel/test-debugger-probe-bound-never-hit(2) -
parallel/test-debugger-probe-text(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'(8) -
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: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(2) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(2) -
Failed to trigger node-test-commit(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 the linked node-test-pull-request jobs and the reliability report at reports/2026-07-02.md, then investigate the listed test and CI failures. Done means the failure causes have been addressed and the corresponding Progress checklist items can be marked complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, devops, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100