CI Reliability 2024-11-03
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/63302 to node-test-pull-request/63396 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-11-03.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-11-03 00:10 | 0 | 16 | 28 | 4 | 52 | 16.67% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-11-03.md to see failure details
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(2) -
Command "git reset --hard" returned status code 128:(3) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(5) -
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) -
fatal error: Killed signal terminated program cc1plus(2) -
sequential/test-http-server-request-timeouts-mixed(13) -
parallel/test-file-write-stream4(6) -
parallel/test-net-write-fully-async-buffer(5) -
parallel/test-stream-readable-unpipe-resume(3) -
parallel/test-http2-large-write-multiple-requests(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-03.md and the linked node-test-pull-request jobs, using the generated ncu-ci walk pr --stats=true --markdown command as the entry point. Review the listed Git, connection, build, reporting, and Node test failures, then verify that the recurring failures no longer affect multiple pull requests.
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