CI Reliability 2026-01-25
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/70911 to node-test-pull-request/71009 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-25.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-25 00:14 | 0 | 20 | 13 | 4 | 63 | 20.83% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-25.md to see failure details
Progress
-
Failed to trigger node-test-commit(2) -
parallel/test-repl-programmatic-history(17) -
parallel/test-inspector-network-http2-compressed(15) -
sequential/test-watch-mode-restart-esm-loading-error(4) -
sequential/test-performance-eventloopdelay(3) -
test-runner/test-run-watch-repeatedly(3) -
wpt/test-streams(3) -
node-api/test_threadsafe_function/test(2) -
parallel/test-fs-watch-recursive-delete(2) -
parallel/test-quic-test-client(2) -
parallel/test-timers-immediate-queue(2) -
parallel/test-zlib-brotli-16GB(2) -
pummel/test-repl-paste-big-data(2) -
sea/test-build-sea(2) -
sea/test-build-sea-executable-field(2) -
test-runner/test-run-watch-dependency-repeatedly(2) -
test-runner/test-run-watch-emit-restarted(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/2026-01-25.md and the linked CI jobs, using the listed ncu-ci walk pr command to inspect failure details. Trace the named failing tests and trigger failure, then address the underlying CI failures until the affected checks no longer reproduce.
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
- 30/100