CI Reliability 2025-07-09
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/67798 to node-test-pull-request/67892 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-07-09.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-07-09 00:12 | 1 | 1 | 27 | 2 | 69 | 1.03% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-07-09.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(10) -
Build timed out (after 60 minutes). Marking the build as failed.(4) -
ERROR: Error fetching remote repo 'origin'(6) -
Command "git reset --hard" returned status code 128:(2) -
fatal: No rebase in progress?(5) -
pummel/test-string-decoder-large-buffer(14) -
parallel/test-runner-watch-mode-kill-signal(9) -
parallel/test-child-process-advanced-serialization-splitted-length-field(6) -
es-module/test-esm-loader-chaining(5) -
es-module/test-esm-loader-event-loop(5) -
es-module/test-esm-loader-hooks(5) -
es-module/test-esm-loader-not-found(5) -
parallel/test-buffer-tostring-range(5) -
parallel/test-string-decoder(5) -
sequential/test-child-process-pass-fd(5) -
parallel/test-worker-message-port-transfer-filehandle(4) -
wpt/test-streams(4) -
es-module/test-esm-loader-default-resolver(3) -
es-module/test-vm-contextified-script-leak(3) -
report/test-report-worker(3) -
parallel/test-fs-cp(2) -
parallel/test-process-threadCpuUsage-worker-threads(2) -
parallel/test-runner-run-watch(2) -
parallel/test-stream-readable-to-web(2) -
parallel/test-url-parse-invalid-input(2) -
parallel/test-v8-coverage(2) -
sequential/test-tls-session-timeout(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/2025-07-09.md and the linked node-test-pull-request Jenkins runs, using the listed failure messages and test names as the investigation entry points. Review each unchecked Progress item and document or address the underlying CI failures until the reported failures are resolved or clearly tracked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100