CI Reliability 2026-04-20
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/72694 to node-test-pull-request/72791 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-20.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-20 00:22 | 1 | 21 | 11 | 2 | 65 | 21.65% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-20.md to see failure details
Progress
-
wpt/test-wasm-jsapi(13) -
sequential/test-performance-eventloopdelay(6) -
wpt/test-streams(4) -
- /home/iojs/build/workspace/node-test-linter/lib/internal/webstreams/util.js(3) -
test-runner/test-run-watch-cwd-isolation-none(3) -
test-runner/test-run-watch-dependency-repeatedly(3) -
wpt/test-hr-time(3) -
async-hooks/test-improper-order(2) -
parallel/test-debugger-heap-profiler(2) -
parallel/test-debugger-probe-global-option-order(2) -
parallel/test-dgram-udp6-link-local-address(2) -
parallel/test-runner-run(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
test-runner/test-run-watch-run-duration(2) -
wpt/test-wasm-webapi(2) -
Build timed out (after 60 minutes). Marking the build as failed.(3) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(4) -
Error: Timed out waiting for restart(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 generated report at reports/2026-04-20.md and the linked node-test-pull-request jobs, then inspect logs for the recurring failures listed in the Progress section. The issue does not define a single fix; work is complete only when the relevant failures are investigated and the corresponding checklist entries can be updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100