CI Reliability 2025-12-03
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/70279 to node-test-pull-request/70371 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-12-03.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-12-03 00:11 | 0 | 12 | 35 | 3 | 50 | 12.37% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-12-03.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(4) -
Failed to trigger sub builds(7) -
ERROR: out of memory(5) -
parallel/test-repl-paste-big-data(6) -
parallel/test-repl-programmatic-history(4) -
parallel/test-quic-test-client(3) -
parallel/test-runner-output(3) -
test-runner/test-run-watch-run-duration(3) -
wasi/test-wasi-pthread(3) -
es-module/test-vm-contextified-script-leak(2) -
sequential/test-without-async-context-frame(2) -
test-runner/test-run-watch-repeatedly(2) -
wpt/test-hr-time(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-12-03.md and the Jenkins runs linked in the issue; group the repeated failure messages and named tests by cause. Investigate the listed CI and test failures, then update the report's progress checklist as each failure is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100