CI Reliability 2026-08-14
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/75724 to node-test-pull-request/75820 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-08-14.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-08-14 00:18 | 1 | 27 | 20 | 6 | 46 | 29.03% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-08-14.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(7) -
fatal: No rebase in progress?(4) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(2) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(2) -
fatal error: error in backend: IO failure on output stream: no space on device(2) -
parallel/test-esm-loader-hooks-inspect-wait(6) -
parallel/test-sqlite-backup(6) -
parallel/test-stream-pipeline-http2(5) -
es-module/test-vm-contextified-script-leak(4) -
ffi/test-ffi-fast-integer-validation(4) -
ffi/test-ffi-fast-buffer(3) -
sequential/test-performance-eventloopdelay(3) -
test-runner/test-run-watch-cwd-isolation-none-argv(2) -
wpt/test-wasm-jsapi(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-08-14.md and the linked node-test-pull-request builds, using the listed failure messages and test names to identify one failure group. The issue was generated with ncu-ci walk pr --stats=true --markdown reports/2026-08-14.md; done means addressing a selected recurring failure and confirming it no longer appears in subsequent CI results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100