CI Reliability 2024-09-21
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/62513 to node-test-pull-request/62612 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-09-21.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-09-21 00:09 | 0 | 21 | 22 | 3 | 54 | 21.65% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-09-21.md to see failure details
Progress
-
Build timed out (after 60 minutes). Marking the build as failed.(2) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(10) -
fatal: No rebase in progress?(6) -
fatal error: Killed signal terminated program cc1plus(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2) -
node-api/test_threadsafe_function/test(9) -
es-module/test-loaders-workers-spawned(6) -
parallel/test-async-context-frame(4) -
parallel/test-runner-watch-mode-complex(4) -
parallel/test-http-remove-header-stays-removed(3) -
parallel/test-http2-large-write-multiple-requests(3) -
parallel/test-buffer-tostring-rangeerror(2) -
parallel/test-cli-node-options(2) -
parallel/test-cli-permission-deny-fs(2) -
pummel/test-hash-seed(2) -
wpt/test-timers(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-09-21.md and the linked CI jobs from node-test-pull-request/62513 through 62612. Review the listed timeout, environment, and test failures, then verify that the recurring failures are resolved in subsequent CI runs and mark the corresponding progress items complete.
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