CI Reliability 2026-04-28
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/72872 to node-test-pull-request/72969 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-28 00:28 | 2 | 16 | 17 | 1 | 64 | 16.49% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-28.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Error fetching remote repo 'origin'(4) -
fatal: No rebase in progress?(5) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
Error: Only one of 'ltcg', 'thin-lto', or 'lto' can be specified.(2) -
parallel/test-sqlite-database-sync(13) -
parallel/test-process-finalization(6) -
sequential/test-debugger-pid(6) -
test-runner/test-run-watch-repeatedly(5) -
parallel/test-debugger-probe-json-preview(4) -
parallel/test-debugger-probe-miss(4) -
sea/test-build-sea(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-assets(4) -
sea/test-single-executable-application-empty(4) -
sea/test-single-executable-application-esm-code-cache(4) -
test-runner/test-run-watch-run-duration(4) -
test-runner/test-run-watch-without-file(4) -
wpt/test-hr-time(4) -
wpt/test-wasm-jsapi(4) -
parallel/test-debugger-probe-child-inspect-port-zero(3) -
parallel/test-debugger-probe-json-special-values(3) -
sea/test-single-executable-application-asset-keys-empty(3) -
sea/test-single-executable-application-assets-raw(3) -
sea/test-single-executable-application-disable-experimental-sea-warning(3) -
sea/test-single-executable-application-esm(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) -
sea/test-single-executable-application-exec-argv-extension-env(3) -
sea/test-single-executable-application-exec-argv-extension-none(3) -
sequential/test-performance-eventloopdelay(3) -
test-runner/test-run-watch-dependency-repeatedly(3) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-debugger-probe-text(2) -
parallel/test-net-autoselectfamily(2) -
sea/test-build-sea-already-exists(2) -
sea/test-single-executable-application-inspect(2) -
sea/test-single-executable-application-snapshot(2) -
test-runner/test-run-watch-cwd-isolation-none(2) -
wasi/test-wasi-pthread(2) -
wpt/test-blob(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-04-28.md and the linked Jenkins jobs to inspect the failure details behind the listed patterns. Reproduce or compare recurring failures such as parallel/test-sqlite-database-sync, test-runner/test-run-watch-repeatedly, and the sea tests. Done means identifying and resolving the relevant CI failures so the affected PR checks pass reliably.
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