CI Reliability 2026-08-22
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/76091 to node-test-pull-request/76188 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-08-22.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-08-22 00:08 | 24 | 6 | 4 | 2 | 64 | 8.11% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-08-22.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(5) -
ERROR: Error fetching remote repo 'origin'(11) -
Command "git fetch --no-tags --force --progress -- git@github.com:nodejs/node.git +refs/heads/*:refs/remotes/origin/* +refs/pull/65291/head:refs/remotes/origin/_jenkins_local_branch" returned status code 128:(7) -
Failed to trigger sub builds(19) -
error: could not apply 61890720c8a... add readme and initial code(11) -
Failed to trigger node-test-commit(9) -
Failed to trigger fanned build(6) -
fatal: No rebase in progress?(2) -
parallel/test-http2-close-while-writing(7) -
parallel/test-stream-pipeline-http2(5) -
parallel/test-fastutf8stream-destroy(4) -
parallel/test-fastutf8stream-reopen(4) -
parallel/test-net-autoselectfamily(2) -
parallel/test-net-listen-ipv6only(2) -
test-runner/test-run-watch-emit-restarted(2) -
wasi/test-wasi-pthread(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 linked reliability report for the node-test-pull-request runs 76091–76188 and compare the listed Jenkins failures. Investigate the reported build, fetch, sub-build, rebase, and named Node.js test failures first. Done means the recurring causes are addressed and the affected CI jobs no longer reproduce these failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, nodejs, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100