CI Reliability 2024-12-09
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/63842 to node-test-pull-request/63940 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-12-09.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-12-09 00:11 | 1 | 17 | 17 | 9 | 56 | 18.89% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-12-09.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) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
sequential/test-http-server-request-timeouts-mixed(10) -
parallel/test-watch-file-shared-dependency(5) -
parallel/test-http-response-status-message(4) -
parallel/test-net-write-fully-async-buffer(3) -
node-api/test_threadsafe_function/test(2) -
parallel/test-abortsignal-drop-settled-signals(2) -
parallel/test-stream-readable-unpipe-resume(2) -
wpt/test-timers(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-12-09.md and the linked node-test-pull-request runs, then inspect the listed Git, ccache, reporting, and test failures. Compare repeated failures across the referenced jobs; done means the progress entries are resolved or have documented follow-up.
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
- 30/100