CI Reliability 2024-11-04
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/63311 to node-test-pull-request/63407 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-11-04.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-11-04 00:10 | 1 | 15 | 28 | 3 | 53 | 15.63% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-11-04.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
ERROR: Error fetching remote repo 'origin'(3) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(3) -
fatal: No rebase in progress?(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
fatal error: Killed signal terminated program cc1plus(2) -
sequential/test-http-server-request-timeouts-mixed(14) -
parallel/test-file-write-stream4(6) -
parallel/test-net-write-fully-async-buffer(6) -
parallel/test-http2-large-write-multiple-requests(2) -
parallel/test-stream-readable-unpipe-resume(2) -
parallel/test-util-getcallsites(2) -
parallel/test-without-async-context-frame(2) -
sequential/test-tls-session-timeout(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-04.md and the Jenkins runs from node-test-pull-request/63311 through 63407. Review the listed infrastructure and test failures, then use the Progress checklist to track investigation; done means the reported recurring failures have been addressed or clearly explained.
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