CI Reliability 2024-09-18
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/62414 to node-test-pull-request/62510 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-18.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-18 00:09 | 3 | 14 | 18 | 1 | 64 | 14.58% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-18.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(6) -
Failed to trigger fanned build(23) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(3) -
parallel/test-http2-large-write-multiple-requests(5) -
node-api/test_threadsafe_function/test(4) -
parallel/test-cli-node-options(2) -
parallel/test-cli-permission-deny-fs(2) -
parallel/test-net-write-fully-async-buffer(2) -
parallel/test-runner-no-isolation-hooks(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/2024-09-18.md and the linked CI jobs, using the listed failure categories to trace which failures affected multiple pull requests. The issue is complete when the reported categories have been investigated and the corresponding Progress items are resolved or clearly accounted for.
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
- 25/100