CI Reliability 2026-01-26
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/70938 to node-test-pull-request/71032 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-26.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-26 00:13 | 1 | 17 | 14 | 5 | 63 | 18.09% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-26.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(3) -
parallel/test-repl-programmatic-history(22) -
parallel/test-inspector-network-http2-compressed(20) -
sequential/test-performance-eventloopdelay(3) -
sequential/test-watch-mode-restart-esm-loading-error(3) -
wpt/test-streams(3) -
es-module/test-vm-contextified-script-leak(2) -
parallel/test-fs-watch-recursive-delete(2) -
parallel/test-timers-immediate-queue(2) -
sea/test-build-sea(2) -
sea/test-build-sea-executable-field(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-26.md and the linked node-test-pull-request jobs from 70938 through 71032. Review the failure details for each unchecked item, including the named Node.js tests and repository errors. Done means the listed recurring failures are addressed and the CI reliability results improve.
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
- Needs clarification
- Newbie friendliness
- 25/100