CI Reliability 2024-11-07
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/63367 to node-test-pull-request/63460 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-11-07.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-11-07 00:09 | 3 | 8 | 34 | 2 | 53 | 8.42% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-11-07.md to see failure details
Progress
-
sequential/test-http-server-request-timeouts-mixed(9) -
parallel/test-file-write-stream4(4) -
parallel/test-net-write-fully-async-buffer(4) -
benchmark/test-benchmark-http2(2) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-os(2) -
parallel/test-stream-readable-unpipe-resume(2) -
parallel/test-util-getcallsites(2) -
parallel/test-without-async-context-frame(2) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Error fetching remote repo 'origin'(3) -
fatal: No rebase in progress?(6) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(3) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(2) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(2) -
Error: list index out of range(2) -
fatal error: Killed signal terminated program cc1plus(2) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(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-11-07.md and compare its failure details with the linked node-test-pull-request jobs. Review the listed test, Jenkins, Git, and build failures, then use the Progress checklist to track which recurring failures have been addressed.
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