CI Reliability 2024-10-14
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/62989 to node-test-pull-request/63087 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2024-10-14.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2024-10-14 00:10 | 0 | 17 | 18 | 12 | 53 | 19.32% |
Open https://github.com/nodejs/reliability/blob/main/reports/2024-10-14.md to see failure details
Progress
-
sequential/test-http-server-request-timeouts-mixed(11) -
wpt/test-compression(7) -
parallel/test-file-write-stream4(3) -
parallel/test-fs-promises-watch(3) -
parallel/test-fs-watch(3) -
parallel/test-fs-watch-recursive-delete(3) -
parallel/test-watch-mode-files_watcher(3) -
pummel/test-fs-watch-non-recursive(3) -
sequential/test-fs-watch(3) -
node-api/test_threadsafe_function/test(2) -
parallel/test-net-write-fully-async-buffer(2) -
Build timed out (after 30 minutes). Marking the build as failed.(9) -
Cannot run program "sh" (in directory "c:\workspace\node-test-binary-windows-js-suites"): CreateProcess error=2, The system cannot find the file specified(5) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(4) -
Error: invalid syntax(3) -
fatal: No rebase in progress?(3) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(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-10-14.md and the linked Jenkins jobs covering builds 62989 through 63087. Review the listed failures, beginning with the repeated test names such as sequential/test-http-server-request-timeouts-mixed and the fs-watch tests. Done means the identified CI failures are addressed and the corresponding progress items can be checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100