CI Reliability 2024-11-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/63400 to node-test-pull-request/63498 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-11-10.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-11-10 00:10 | 0 | 11 | 30 | 9 | 50 | 12.09% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-11-10.md to see failure details
Progress
-
sequential/test-http-server-request-timeouts-mixed(10) -
parallel/test-file-write-stream4(3) -
parallel/test-stream-readable-unpipe-resume(3) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-os(2) -
pummel/test-fs-readfile-tostring-fail(2) -
ERROR: Error fetching remote repo 'origin'(2) -
fatal: No rebase in progress?(5) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(2) -
Error: Command failed: /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/out/Release/node /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/deps/npm/node_modules/node-gyp/bin/node-gyp.js rebuild --directory=/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/benchmark/napi/function_args(2) -
Error: Command failed: /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/out/Release/node /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/deps/npm/node_modules/node-gyp/bin/node-gyp.js rebuild --directory=/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/benchmark/napi/function_call(2) -
Error: list index out of range(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-10.md and the linked Jenkins jobs for the listed failures. Review the generated failure details and the affected Node.js tests, including sequential/test-http-server-request-timeouts-mixed and parallel/test-file-write-stream4. Done means identifying and resolving the recurring CI failures so the affected jobs pass reliably.
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
- 20/100