CI Reliability 2024-09-10
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/62137 to node-test-pull-request/62206 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-10.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-10 00:09 | 22 | 3 | 0 | 63 | 12 | 20.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-10.md to see failure details
Progress
-
fatal error: /Library/Developer/CommandLineTools/usr/bin/libtool: can't write to output file (No space left on device)(5)
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/2024-09-10.md at the linked reliability report and review the node-test-pull-request runs from 62137 through 62206. Focus on the repeated macOS libtool “No space left on device” failure and its five affected PRs. Done means the cause is identified and the listed CI failure no longer recurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100