CI Reliability 2026-07-30
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/75202 to node-test-pull-request/75296 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-07-30.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-07-30 00:25 | 1 | 16 | 25 | 8 | 50 | 17.58% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-07-30.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(3) -
Failed to trigger fanned build(10) -
sh: line 12: [: -gt: unary operator expected(6) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(4) -
Failed to trigger node-test-commit(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2) -
parallel/test-vfs-readdir-symlink-recursive(4) -
test-runner/test-run-watch-cwd-isolation-none-argv(3) -
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)
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-07-30.md and the linked node-test-pull-request jobs, then review the output from ncu-ci walk pr --stats=true --markdown reports/2026-07-30.md. The issue lists many independent infrastructure and test failures, so done means investigating and checking off the listed failure categories after the relevant CI failures no longer recur.
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
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100