CI Reliability 2024-12-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/63870 to node-test-pull-request/63966 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-12-10.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-12-10 00:11 | 1 | 16 | 19 | 9 | 55 | 17.78% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-12-10.md to see failure details
Progress
-
Command "git reset --hard" returned status code 128:(2) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(4) -
sequential/test-http-server-request-timeouts-mixed(11) -
parallel/test-abortsignal-drop-settled-signals(8) -
parallel/test-watch-file-shared-dependency(6) -
parallel/test-net-write-fully-async-buffer(4) -
parallel/test-http-response-status-message(3) -
parallel/test-stream-readable-unpipe-resume(3) -
node-api/test_threadsafe_function/test(2) -
parallel/test-file-write-stream4(2) -
pummel/test-hash-seed(2) -
sequential/test-tls-session-timeout(2) -
wpt/test-compression(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 the linked CI job range and the failure details in reports/2024-12-10.md, generated by ncu-ci walk pr --stats=true --markdown reports/2024-12-10.md. Review the listed Git and Node.js test failures to identify their causes. Done means the tracked failures are addressed and the progress checklist can be updated.
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