CI Reliability 2026-06-04
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/73805 to node-test-pull-request/73904 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-04.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-06-04 00:45 | 0 | 24 | 21 | 1 | 54 | 24.24% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-06-04.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(6) -
Failed to trigger sub builds(6) -
fatal: No rebase in progress?(4) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
Error: Timed out waiting for restart(2) -
Failed to trigger fanned build(2) -
parallel/test-fs-watch-recursive-delete(4) -
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) -
parallel/test-cluster-dgram-reuse(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-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-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-04.md and the linked node-test-pull-request builds 73805–73904; use the failure details to group the CI and Node test failures listed in the Progress checklist. Done would require determining the cause and resolving the recurring failures, but the issue does not identify a single entry point or acceptance test.
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