CI Reliability 2024-11-13
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/63433 to node-test-pull-request/63524 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-11-13.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-11-13 00:09 | 4 | 14 | 22 | 11 | 49 | 16.47% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-11-13.md to see failure details
Progress
-
sequential/test-http-server-request-timeouts-mixed(8) -
parallel/test-stream-readable-unpipe-resume(7) -
parallel/test-file-write-stream4(4) -
parallel/test-cluster-fork-stdio(3) -
wpt/test-compression(3) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-module-loading-globalpaths(2) -
parallel/test-module-stat(2) -
parallel/test-os(2) -
pummel/test-fs-readfile-tostring-fail(2) -
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: 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) -
fatal: No rebase in progress?(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 the linked reliability report for the failures from node-test-pull-request/63433 through 63524, then inspect the listed test and CI errors. Work through the failure details and use the Progress checklist to track which recurring failures have been addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100