CI Reliability 2025-12-26
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/70504 to node-test-pull-request/70601 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-12-26.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-12-26 00:12 | 0 | 10 | 28 | 1 | 61 | 10.10% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-12-26.md to see failure details
Progress
-
parallel/test-repl-programmatic-history(6) -
parallel/test-quic-test-client(5) -
sequential/test-performance-eventloopdelay(5) -
test-runner/test-run-watch-without-file(4) -
wpt/test-hr-time(4) -
async-hooks/test-improper-order(3) -
test-runner/test-run-watch-run-duration(3) -
async-hooks/test-emit-after-on-destroyed(2) -
parallel/test-fs-stat-bigint(2) -
test-runner/test-run-watch-dependency-repeatedly(2) -
Build timed out (after 60 minutes). Marking the build as failed.(3) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
Build timed out (after 30 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(9) -
Failed to trigger node-test-commit(3) -
ERROR: Step �Archive the artifacts� failed: no workspace for ...(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 node-test-pull-request builds and the reliability report at reports/2025-12-26.md. Review the listed failures, including the parallel, sequential, WPT, async-hooks, test-runner, timeout, and repository-fetch errors, then reproduce the relevant failures. Done means the reported CI failures are resolved and the affected checks complete reliably.
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
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100