CI Reliability 2025-02-12
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/65038 to node-test-pull-request/65140 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2025-02-12.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2025-02-12 00:10 | 3 | 19 | 15 | 20 | 43 | 24.68% |
Open https://github.com/nodejs/reliability/blob/main/reports/2025-02-12.md to see failure details
Progress
-
parallel/test-assert-fail(6) -
parallel/test-net-write-fully-async-buffer(5) -
parallel/test-file-write-stream4(4) -
parallel/test-net-write-fully-async-hex-string(4) -
parallel/test-runner-run-watch(4) -
sequential/test-perf-hooks(3) -
benchmark/test-benchmark-http2(2) -
parallel/test-runner-output(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)
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 failure details in reports/2025-02-12.md and review the listed failures, including parallel/test-assert-fail and parallel/test-net-write-fully-async-buffer. Use the referenced node-test-pull-request jobs and the ncu-ci walk command output to trace repeated failures. Done means the listed failures are investigated and the relevant CI issues are resolved or documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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