CI Reliability 2026-07-28
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/75130 to node-test-pull-request/75209 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-07-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-07-28 00:25 | 19 | 4 | 1 | 4 | 72 | 5.19% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-07-28.md to see failure details
Progress
-
parallel/test-repl-user-error-handler(4) -
parallel/test-crypto-x509(2) -
parallel/test-http2-reset-happy-close(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-empty(2) -
sea/test-single-executable-application-exec-argv-extension-cli(2) -
sea/test-single-executable-application-exec-argv-extension-env(2) -
Failed to trigger fanned build(37) -
error: could not apply 61890720c8a... add readme and initial code(14) -
fatal: No rebase in progress?(9) -
error: could not apply 4f844f4380a... repl: use inspector over vm(7)
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 the linked reports/2026-07-28.md report and the Jenkins job range node-test-pull-request/75130 through 75209. Review the listed failing tests and build or rebase errors to determine their causes; done means the failures are resolved and the corresponding Progress items can be checked off.
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