CI Reliability 2026-01-17
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/70743 to node-test-pull-request/70841 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-01-17.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-01-17 00:12 | 1 | 12 | 25 | 3 | 59 | 12.50% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-01-17.md to see failure details
Progress
-
node-api/test_threadsafe_function/test(13) -
parallel/test-repl-programmatic-history(12) -
parallel/test-quic-test-client(4) -
parallel/test-crypto-dh-generate-keys(3) -
test-runner/test-run-watch-cwd-isolation-none(3) -
wpt/test-wasm-webapi(3) -
async-hooks/test-emit-before-on-destroyed(2) -
client-proxy/test-https-proxy-request-invalid-char-in-url(2) -
parallel/test-domain-http-server(2) -
parallel/test-http2-close-while-writing(2) -
test-runner/test-run-watch-repeatedly(2) -
wpt/test-streams(2) -
wpt/test-webcrypto(2) -
Build timed out (after 30 minutes). Marking the build as failed.(4) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Error fetching remote repo 'origin'(4) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(2) -
fatal: No rebase in progress?(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 linked reports/2026-01-17.md failure details and the listed CI failures, then review how ncu-ci walk pr --stats=true --markdown generated the report. Investigate the repeated failures and update the progress list as they are addressed; the issue is complete when the listed reliability problems have been resolved or otherwise accounted for.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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