CI Reliability 2026-06-15
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/74037 to node-test-pull-request/74136 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-06-15.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-06-15 00:41 | 0 | 23 | 15 | 1 | 61 | 23.23% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-06-15.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(4) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(3) -
error: could not apply 61890720c8a... add readme and initial code(2) -
fatal: no rebase in progress(2) -
addons/worker-addon-exit/test(12) -
parallel/test-debugger-probe-failure-process-exit(2) -
sea/test-build-sea(2) -
sea/test-build-sea-already-exists(2) -
sea/test-build-sea-custom-argv0(2) -
sea/test-build-sea-executable-field(2) -
sea/test-build-sea-missing-output(2) -
sea/test-single-executable-application-asset-keys(2) -
sea/test-single-executable-application-asset-keys-empty(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-extension-cli(2) -
wpt/test-streams(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-15.md and the linked CI job range, generated by ncu-ci walk pr --stats=true --markdown reports/2026-06-15.md. Investigate the listed recurring failures, especially addons/worker-addon-exit/test, the SEA tests, and the infrastructure errors. Done means the identified failures are fixed or accounted for and the affected CI jobs no longer reproduce them.
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
- 28/100