CI Reliability 2026-06-06
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/73830 to node-test-pull-request/73926 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-06.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-06-06 00:36 | 0 | 19 | 16 | 2 | 63 | 19.39% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-06-06.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(5) -
Failed to trigger fanned build(9) -
Failed to trigger sub builds(7) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
Error: Timed out waiting for restart(2) -
fatal: No rebase in progress?(2) -
parallel/test-fs-watch-recursive-delete(3) -
sea/test-build-sea(3) -
sea/test-build-sea-already-exists(3) -
sea/test-build-sea-custom-argv0(3) -
sea/test-build-sea-executable-field(3) -
sea/test-build-sea-missing-output(3) -
sea/test-single-executable-application-asset-keys(3) -
sea/test-single-executable-application-asset-keys-empty(3) -
sea/test-single-executable-application-exec-argv-extension-cli(3) -
sea/test-single-executable-application-exec-argv-extension-env(3) -
sea/test-single-executable-application-inspect(3) -
addons/worker-addon-exit/test(2) -
parallel/test-cluster-dgram-reuse(2) -
parallel/test-debugger-probe-failure-process-exit(2) -
parallel/test-http-server-consumed-timeout(2) -
parallel/test-watch-mode-files_watcher(2) -
sea/test-single-executable-application-assets(2) -
sea/test-single-executable-application-assets-raw(2) -
sea/test-single-executable-application-disable-experimental-sea-warning(2) -
sea/test-single-executable-application-empty(2) -
sea/test-single-executable-application-esm(2) -
sea/test-single-executable-application-esm-code-cache(2) -
sea/test-single-executable-application-exec-argv(2) -
sea/test-single-executable-application-exec-argv-empty(2) -
sea/test-single-executable-application-exec-argv-extension-none(2) -
sea/test-single-executable-application-inspect-in-sea-flags(2) -
sea/test-single-executable-application-snapshot-and-code-cache(2) -
sea/test-single-executable-application-use-code-cache(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-06-06.md and the linked node-test-pull-request builds to investigate the repeated failures listed in the Progress section. Use the generated ncu-ci command context to compare failure details across the reported builds. Done means the identified CI failure categories are resolved and the affected pull requests can complete reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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