CI Reliability 2026-07-25
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/75015 to node-test-pull-request/75107 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-07-25.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-07-25 00:28 | 3 | 18 | 7 | 6 | 66 | 19.78% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-07-25.md to see failure details
Progress
-
parallel/test-repl-user-error-handler(25) -
client-proxy/test-https-proxy-request-invalid-char-in-url(4) -
parallel/test-runner-run-watch(4) -
parallel/test-runner-watch-mode(4) -
sequential/test-performance-eventloopdelay(4) -
parallel/test-http2-socket-proxy-destroy(3) -
parallel/test-http2-reset-happy-close(2) -
parallel/test-vfs-readdir-symlink-recursive(2) -
sea/test-single-executable-application-disable-experimental-sea-warning(2) -
test-runner/test-run-watch-cwd-isolation-none-argv(2) -
test-runner/test-run-watch-emit-restarted(2) -
ERROR: Error fetching remote repo 'origin'(5) -
Command "git fetch --no-tags --force --progress -- git@github.com:nodejs/node.git +refs/heads/*:refs/remotes/origin/* +refs/pull/64399/head:refs/remotes/origin/_jenkins_local_branch" returned status code 128:(2) -
fatal: No rebase in progress?(17) -
error: could not apply 61890720c8a... add readme and initial code(15) -
sh: line 12: [: -gt: unary operator expected(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(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-07-25.md and the linked CI jobs to inspect the failure details for the unchecked test and Jenkins errors. Work through the listed failures, then verify the affected CI runs no longer reproduce them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, nodejs, 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
- 38/100