CI Reliability 2025-12-07
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/70311 to node-test-pull-request/70405 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-12-07.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-12-07 00:13 | 2 | 6 | 36 | 4 | 52 | 6.38% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-12-07.md to see failure details
Progress
-
parallel/test-repl-paste-big-data(5) -
parallel/test-repl-programmatic-history(5) -
parallel/test-util-styletext(3) -
sequential/test-without-async-context-frame(3) -
parallel/test-child-process-fork-closed-channel-segfault(2) -
test-runner/test-run-watch-run-duration(2) -
wpt/test-wasm-webapi(2) -
Build timed out (after 60 minutes). Marking the build as failed.(3) -
ERROR: Error fetching remote repo 'origin'(7) -
ERROR: out of memory(5)
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-07.md and the linked node-test-pull-request runs; compare the listed failures with the Progress checklist. Investigate each repeated test or infrastructure error and record fixes or follow-up status, with the CI failures no longer recurring as the completion signal.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100