CI Reliability 2025-09-26
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/69282 to node-test-pull-request/69379 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-09-26.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-09-26 00:11 | 1 | 12 | 19 | 7 | 61 | 13.04% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-09-26.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(6) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(3) -
Failed to trigger node-test-commit(2) -
sequential/test-single-executable-application(20) -
sequential/test-single-executable-application-asset-keys(20) -
sequential/test-single-executable-application-asset-keys-empty(20) -
sequential/test-single-executable-application-assets(20) -
sequential/test-single-executable-application-assets-raw(20) -
sequential/test-single-executable-application-disable-experimental-sea-warning(20) -
sequential/test-single-executable-application-exec-argv(20) -
sequential/test-single-executable-application-exec-argv-empty(20) -
sequential/test-single-executable-application-exec-argv-extension-cli(20) -
sequential/test-single-executable-application-exec-argv-extension-env(20) -
sequential/test-single-executable-application-exec-argv-extension-none(20) -
sequential/test-single-executable-application-inspect(20) -
sequential/test-single-executable-application-inspect-in-sea-flags(20) -
sequential/test-single-executable-application-snapshot(20) -
sequential/test-single-executable-application-snapshot-and-code-cache(20) -
sequential/test-single-executable-application-snapshot-worker(20) -
sequential/test-single-executable-application-use-code-cache(20) -
parallel/test-runner-run-watch(14) -
parallel/test-runner-watch-mode-kill-signal(6) -
client-proxy/test-https-proxy-request-invalid-char-in-url(5) -
parallel/test-without-async-context-frame(5) -
sequential/test-perf-hooks(5) -
parallel/test-fs-promises-watch-iterator(3) -
parallel/test-http2-close-while-writing(2) -
sequential/test-performance-eventloopdelay(2) -
wpt/test-hr-time(2) -
wpt/test-streams(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 reports/2025-09-26.md and the linked node-test-pull-request runs. Review the listed CI and test failures, especially the repeated single-executable-application failures, and determine the appropriate follow-up. The issue is complete when the causes are addressed and the Progress checklist reflects the results.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100