CI Reliability 2025-02-11
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/65026 to node-test-pull-request/65131 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-11.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-02-11 00:09 | 5 | 18 | 15 | 19 | 43 | 23.68% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-02-11.md to see failure details
Progress
-
parallel/test-assert-fail(6) -
parallel/test-net-write-fully-async-buffer(5) -
parallel/test-net-write-fully-async-hex-string(4) -
parallel/test-runner-run-watch(4) -
parallel/test-file-write-stream4(3) -
parallel/test-runner-output(2) -
sequential/test-perf-hooks(2) -
sequential/test-vm-timeout-escape-promise-module-2(2) -
Cannot run program "/bin/sh" (in directory "/home/iojs/build/workspace/node"): error=0, Failed to exec spawn helper: pid: 2228979, exit value: 1(2) -
ERROR: Error fetching remote repo 'origin'(4) -
error: remote GitHub already exists.(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
Read reports/2025-02-11.md and the linked CI runs, then inspect the listed failing Node.js tests and CI errors. Done means the tracked failures have been investigated and the progress list reflects their status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100