CI Reliability 2025-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/64444 to node-test-pull-request/64539 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-17.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-01-17 00:10 | 0 | 22 | 24 | 5 | 49 | 23.16% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-01-17.md to see failure details
Progress
-
parallel/test-net-write-fully-async-buffer(7) -
parallel/test-net-write-fully-async-hex-string(7) -
sequential/test-worker-prof(7) -
parallel/test-buffer-tostring-rangeerror(6) -
es-module/test-wasm-web-api(4) -
parallel/test-file-write-stream4(3) -
parallel/test-without-async-context-frame(3) -
pummel/test-heapdump-http2(3) -
sequential/test-http-server-request-timeouts-mixed(3) -
- /home/iojs/build/workspace/node-test-linter/test/parallel/test-crypto-oneshot-hash.js(2) -
sequential/test-tls-session-timeout(2) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(3) -
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(6) -
fatal: Could not read from remote repository.(4) -
fatal: unable to access 'https://github.com/nodejs/build.git/': The requested URL returned error: 500(4) -
fatal: unable to access 'https://github.com/nodejs/build.git/': The requested URL returned error: 502(3)
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 by reading reports/2025-01-17.md and the linked CI job range, then investigate the listed recurring test and repository-access failures. Done means the reported failures have been addressed and the corresponding progress items can be checked off.
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