CI Reliability 2026-06-26
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/74320 to node-test-pull-request/74416 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-26.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-06-26 00:38 | 0 | 20 | 32 | 1 | 47 | 20.20% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-06-26.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(8) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2) -
sea/test-single-executable-application-empty(6) -
test-runner/test-run-watch-cwd-isolation-none-argv(4) -
parallel/test-http-server-consumed-timeout(3) -
parallel/test-blob(2) -
parallel/test-heapsnapshot-near-heap-limit-worker(2) -
parallel/test-sqlite-backup(2) -
parallel/test-web-locks(2) -
sea/test-build-sea-custom-argv0(2) -
sea/test-single-executable-application-asset-keys(2) -
sea/test-single-executable-application-exec-argv-extension-cli(2) -
sea/test-single-executable-application-inspect(2) -
sea/test-single-executable-application-snapshot(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 Jenkins jobs and the failure details in reports/2026-06-26.md, generated by ncu-ci walk pr --stats=true --markdown reports/2026-06-26.md. Investigate the listed remote-repository, test-report, and named test failures; done means the recurring failures are addressed and CI is green again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, 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