CI Reliability 2025-07-08
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/67781 to node-test-pull-request/67878 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-07-08.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-07-08 00:12 | 0 | 1 | 25 | 1 | 73 | 1.01% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-07-08.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(9) -
Build timed out (after 60 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(6) -
Command "git reset --hard" returned status code 128:(2) -
fatal: No rebase in progress?(4) -
pummel/test-string-decoder-large-buffer(17) -
parallel/test-runner-watch-mode-kill-signal(15) -
parallel/test-child-process-advanced-serialization-splitted-length-field(8) -
es-module/test-esm-loader-hooks(5) -
parallel/test-buffer-tostring-range(5) -
parallel/test-config-file(5) -
parallel/test-string-decoder(5) -
parallel/test-worker-message-port-transfer-filehandle(5) -
sequential/test-child-process-pass-fd(5) -
es-module/test-esm-loader-chaining(4) -
es-module/test-esm-loader-event-loop(4) -
es-module/test-esm-loader-not-found(4) -
es-module/test-esm-loader-default-resolver(3) -
es-module/test-vm-contextified-script-leak(3) -
report/test-report-worker(3) -
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) -
wpt/test-streams(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-08.md and the linked Jenkins builds from node-test-pull-request/67781 through 67878. Reproduce the listed test failures and investigate the timeout, repository-fetch, reset, and rebase errors. Done means the identified recurring failures are resolved and the affected CI jobs no longer fail repeatedly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, nodejs, shell
- Domain
- ci-cd, devops, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100