CI Reliability 2026-07-06
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/74474 to node-test-pull-request/74572 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-07-06.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-07-06 00:31 | 5 | 23 | 12 | 5 | 55 | 25.56% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-07-06.md to see failure details
Progress
-
test-runner/test-run-watch-cwd-isolation-none-argv(9) -
parallel/test-npm-install(8) -
parallel/test-debugger-probe-failure-process-exit(5) -
sea/test-single-executable-application(5) -
parallel/test-debugger-probe-max-hit-partial(3) -
sea/test-single-executable-application-empty(3) -
parallel/test-debugger-probe-bound-never-hit(2) -
parallel/test-debugger-probe-expression-throws(2) -
parallel/test-debugger-probe-script-throws(2) -
parallel/test-esm-loader-hooks-inspect-wait(2) -
test-runner/test-run-watch-emit-restarted(2) -
wasi/test-wasi-pthread(2) -
ERROR: Error fetching remote repo 'origin'(5) -
Command "git reset --hard" returned status code 128:(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2) -
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)
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
Read reports/2026-07-06.md and the linked node-test-pull-request runs from 74474 to 74572. Start by reproducing one recurring failure from the Progress list and trace its CI job output. Done means the recurring failures are addressed and the corresponding progress entries are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, 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