CI Reliability 2026-04-19
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/72679 to node-test-pull-request/72776 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-04-19.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-04-19 00:23 | 0 | 20 | 11 | 3 | 66 | 20.62% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-04-19.md to see failure details
Progress
-
wpt/test-wasm-jsapi(13) -
parallel/test-watch-mode-files_watcher(6) -
pummel/test-fs-watch-non-recursive(6) -
sequential/test-fs-watch(6) -
sequential/test-performance-eventloopdelay(6) -
parallel/test-fs-watch-recursive-delete(5) -
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-dgram-udp6-link-local-address(2) -
parallel/test-fs-promises-watch(2) -
parallel/test-fs-watch(2) -
parallel/test-fs-watch-enoent(2) -
parallel/test-runner-run(2) -
parallel/test-worker-nearheaplimit-deadlock(2) -
sequential/test-debugger-pid(2) -
test-runner/test-run-watch-run-duration(2) -
wasm-allocation/test-wasm-allocation(2) -
wasm-allocation/test-wasm-allocation-memory64(2) -
wpt/test-wasm-webapi(2) -
Build timed out (after 60 minutes). Marking the build as failed.(3) -
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(4) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
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 reports/2026-04-19.md and the linked node-test-pull-request builds, then inspect the listed failing tests and infrastructure errors. The issue groups many failures across watch mode, WebAssembly, test runner, filesystem, and CI setup, without identifying a single change. Done means the unchecked progress items have been investigated and the corresponding CI failures are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100