CI Reliability 2025-02-02
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/64808 to node-test-pull-request/64902 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-02.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-02-02 00:10 | 0 | 19 | 8 | 15 | 58 | 22.35% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-02-02.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(2) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(5) -
fatal error: Killed signal terminated program cc1plus(4) -
Error: list index out of range(2) -
Unknown(2) -
parallel/test-assert-fail(11) -
parallel/test-runner-run-watch(10) -
parallel/test-net-write-fully-async-buffer(8) -
parallel/test-buffer-tostring-rangeerror(5) -
parallel/test-net-write-fully-async-hex-string(5) -
parallel/test-permission-fs-read(5) -
parallel/test-permission-fs-write(5) -
parallel/test-runner-output(5) -
parallel/test-file-write-stream4(4) -
parallel/test-pipe-file-to-http(4) -
wpt/test-url(4) -
parallel/test-child-process-bad-stdio(3) -
parallel/test-cluster-fork-stdio(3) -
parallel/test-stream-readable-unpipe-resume(3) -
sequential/test-perf-hooks(3) -
wpt/test-compression(3) -
parallel/test-buffer-tostring-range(2) -
parallel/test-esm-loader-hooks-inspect-wait(2) -
parallel/test-process-threadCpuUsage-worker-threads(2) -
parallel/test-zlib-brotli-16GB(2) -
sequential/test-tls-session-timeout(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-02-02.md and the linked node-test-pull-request runs, then review the listed failure messages and test names. The work is complete when the reported failures have been investigated and the corresponding Progress items can be updated with their status or resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, 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