CI Reliability 2026-06-03
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/73801 to node-test-pull-request/73898 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-03.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-06-03 00:45 | 1 | 26 | 20 | 2 | 51 | 26.80% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-06-03.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(6) -
Command "git reset --hard" returned status code 128:(2) -
Failed to trigger sub builds(6) -
fatal: No rebase in progress?(4) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(2) -
Error: Timed out waiting for restart(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) -
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-03.md and the failures linked from node-test-pull-request/73801 through 73898; the issue was generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-03.md. Review the listed CI errors and SEA and filesystem-watch test failures, then verify that the affected failures no longer recur in subsequent CI runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, nodejs, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100