CI Reliability 2026-02-05
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/71097 to node-test-pull-request/71196 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-02-05.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-02-05 00:16 | 0 | 22 | 22 | 4 | 52 | 22.92% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-02-05.md to see failure details
Progress
-
parallel/test-repl-programmatic-history(14) -
sequential/test-watch-mode-restart-esm-loading-error(8) -
parallel/test-child-process-fork-exec-path(4) -
parallel/test-file-write-stream4(4) -
parallel/test-module-loading-globalpaths(4) -
sequential/test-performance-eventloopdelay(4) -
wpt/test-hr-time(4) -
parallel/test-runner-output(3) -
benchmark/test-benchmark-esm(2) -
parallel/test-crypto-dh-generate-keys(2) -
parallel/test-http-client-response-domain(2) -
parallel/test-node-output-sourcemaps(2) -
parallel/test-promise-reject-callback-exception(2) -
parallel/test-repl-history-navigation(2) -
parallel/test-repl-load-multiline-from-history(2) -
parallel/test-repl-multiline-navigation(2) -
parallel/test-repl-multiline-navigation-while-adding(2) -
parallel/test-repl-null(2) -
parallel/test-repl-options(2) -
parallel/test-repl-persistent-history(2) -
test-runner/test-run-watch-without-file(2) -
Failed to trigger sub builds(3) -
fatal: No rebase in progress?(3)
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-02-05.md and the linked CI jobs to inspect the failure details for the listed tests. Work through the recurring failures and mark each resolved item in the Progress list; done means the reported failures no longer recur across the affected pull requests.
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
- Mostly clear
- Newbie friendliness
- 25/100