CI Reliability 2025-01-16
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/64428 to node-test-pull-request/64522 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-01-16.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-01-16 00:10 | 1 | 19 | 24 | 5 | 51 | 20.21% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-01-16.md to see failure details
Progress
-
sequential/test-worker-prof(8) -
parallel/test-net-write-fully-async-buffer(7) -
parallel/test-net-write-fully-async-hex-string(7) -
parallel/test-buffer-tostring-rangeerror(5) -
es-module/test-wasm-web-api(4) -
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) -
parallel/test-file-write-stream4(2) -
parallel/test-without-async-context-frame(2) -
sequential/test-performance-eventloopdelay(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?(5) -
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 with reports/2025-01-16.md and the linked CI runs for failure details. Then inspect the listed failing tests, including sequential/test-worker-prof and parallel/test-net-write-fully-async-buffer, along with the repository and connection errors. Done means the listed recurring failures are investigated and the progress checklist is resolved.
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
- 30/100