CI Reliability 2026-06-09
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/73886 to node-test-pull-request/73982 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-09.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-06-09 00:33 | 0 | 24 | 10 | 4 | 62 | 25.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-06-09.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(5) -
Failed to trigger fanned build(9) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
fatal: No rebase in progress?(2) -
sea/test-build-sea(4) -
sea/test-build-sea-already-exists(4) -
sea/test-build-sea-custom-argv0(4) -
sea/test-build-sea-executable-field(4) -
sea/test-build-sea-missing-output(4) -
sea/test-single-executable-application-asset-keys(4) -
sea/test-single-executable-application-asset-keys-empty(4) -
sea/test-single-executable-application-assets(4) -
sea/test-single-executable-application-assets-raw(4) -
sea/test-single-executable-application-exec-argv(4) -
sea/test-single-executable-application-exec-argv-extension-cli(4) -
sea/test-single-executable-application-exec-argv-extension-env(4) -
sea/test-single-executable-application-exec-argv-extension-none(4) -
sea/test-single-executable-application-inspect(4) -
sea/test-single-executable-application-disable-experimental-sea-warning(3) -
sea/test-single-executable-application-empty(3) -
sea/test-single-executable-application-esm(3) -
sea/test-single-executable-application-esm-code-cache(3) -
sea/test-single-executable-application-exec-argv-empty(3) -
sea/test-single-executable-application-snapshot(3) -
sea/test-single-executable-application-snapshot-and-code-cache(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) -
sea/test-single-executable-application-inspect-in-sea-flags(2) -
sea/test-single-executable-application-snapshot-worker(2) -
wasi/test-wasi-poll(2) -
wpt/test-webcrypto(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-09.md and the linked CI jobs to identify one failure pattern, then inspect the named test suites such as sea and parallel. Reproduce the selected failure in the CI workflow and trace its existing test or build entry point. Done means the selected recurring failure is addressed and the affected CI jobs pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100