CI Reliability 2026-05-01
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/72954 to node-test-pull-request/73052 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-05-01.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-05-01 00:31 | 0 | 19 | 16 | 4 | 61 | 19.79% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-05-01.md to see failure details
Progress
-
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(4) -
fatal: no rebase in progress(4) -
fatal: No rebase in progress?(3) -
Failed to trigger fanned build(2) -
parallel/test-sqlite-database-sync(19) -
parallel/test-process-finalization(6) -
sequential/test-performance-eventloopdelay(5) -
parallel/test-runner-watch-mode(4) -
sequential/test-watch-mode-worker(4) -
sea/test-build-sea(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-assets(3) -
sea/test-single-executable-application-assets-raw(3) -
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(3) -
sea/test-single-executable-application-exec-argv-empty(3) -
sea/test-single-executable-application-exec-argv-extension-cli(3) -
parallel/test-blob(2) -
parallel/test-http2-close-while-writing(2) -
sea/test-build-sea-already-exists(2) -
sea/test-single-executable-application-exec-argv-extension-env(2) -
sea/test-single-executable-application-exec-argv-extension-none(2) -
sea/test-single-executable-application-snapshot(2) -
test-runner/test-output-test-runner-watch-spec(2) -
test-runner/test-run-watch-run-duration(2) -
wasi/test-wasi-poll(2) -
wpt/test-hr-time(2) -
wpt/test-timers(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 the generated report at reports/2026-05-01.md and reproduce or inspect the failures from the linked CI jobs, using the ncu-ci walk pr --stats=true --markdown command shown in the issue. Work through the listed recurring failures and regenerate the report to confirm that the affected CI jobs are reliable.
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
- 35/100