CI Reliability 2026-02-22
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/71297 to node-test-pull-request/71393 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-02-22.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-02-22 00:15 | 1 | 17 | 24 | 4 | 54 | 17.89% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-02-22.md to see failure details
Progress
-
Failed to create a temp file on /home/iojs/build/workspace/node(4) -
Build timed out (after 60 minutes). Marking the build as failed.(3) -
Unexpected termination of the channel(3) -
fatal: No rebase in progress?(4) -
ERROR: Error fetching remote repo 'origin'(4) -
wpt/test-hr-time(5) -
parallel/test-child-process-fork-exec-path(3) -
parallel/test-file-write-stream4(3) -
parallel/test-http-client-response-domain(3) -
parallel/test-module-loading-globalpaths(3) -
parallel/test-promise-reject-callback-exception(3) -
sequential/test-performance-eventloopdelay(3) -
test-runner/test-run-watch-emit-restarted(3) -
test-runner/test-run-watch-without-file(3) -
benchmark/test-benchmark-esm(2) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-child-process-fork-closed-channel-segfault(2) -
parallel/test-runner-run-watch(2) -
parallel/test-runner-watch-mode(2) -
parallel/test-strace-openat-openssl(2) -
parallel/test-vm-sigint(2) -
test-runner/test-run-watch-dependency-repeatedly(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-02-22.md and the linked node-test-pull-request runs, using the listed failure names as entry points. Run or inspect ncu-ci walk pr --stats=true --markdown reports/2026-02-22.md to compare the failures and reproduce the named tests. Done means the reported CI failures are investigated and the corresponding progress items are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, 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
- 35/100