CI Reliability 2026-08-17
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/75799 to node-test-pull-request/75898 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-08-17.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-08-17 00:07 | 0 | 21 | 19 | 1 | 59 | 21.21% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-08-17.md to see failure details
Progress
-
Build timed out (after 30 minutes). Marking the build as failed.(5) -
Build timed out (after 120 minutes). Marking the build as failed.(2) -
fatal: No rebase in progress?(8) -
error: could not apply 61890720c8a... add readme and initial code(6) -
fatal: no rebase in progress(4) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2) -
ffi/test-ffi-fast-integer-validation(8) -
sea/test-build-sea(5) -
sea/test-build-sea-missing-output(5) -
sea/test-single-executable-application-asset-keys(5) -
sea/test-single-executable-application-asset-keys-empty(5) -
sea/test-single-executable-application-assets(5) -
sea/test-single-executable-application-disable-experimental-sea-warning(5) -
parallel/test-stream-pipeline-http2(4) -
sea/test-build-sea-already-exists(4) -
sea/test-build-sea-custom-argv0(4) -
sea/test-build-sea-executable-field(4) -
sea/test-single-executable-application-assets-raw(4) -
sea/test-single-executable-application-empty(4) -
sea/test-single-executable-application-esm-code-cache(4) -
sea/test-single-executable-application-exec-argv(4) -
sea/test-single-executable-application-exec-argv-empty(4) -
sequential/test-performance-eventloopdelay(4) -
es-module/test-vm-contextified-script-leak(3) -
parallel/test-debugger-extract-function-name(3) -
sea/test-single-executable-application-esm(3) -
sea/test-single-executable-application-exec-argv-extension-cli(3) -
sea/test-single-executable-application-exec-argv-extension-env(3) -
parallel/test-inspect-async-hook-setup-at-inspect(2) -
parallel/test-inspector-connect-to-main-thread(2) -
parallel/test-runner-coverage(2) -
parallel/test-sqlite-backup(2) -
sea/test-single-executable-application-exec-argv-extension-none(2) -
sea/test-single-executable-application-inspect(2) -
sea/test-single-executable-application-inspect-in-sea-flags(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 and the node-test-pull-request jobs to inspect the listed failure details. Group recurring failures such as timeouts, rebase errors, and named test failures, then reproduce the relevant jobs or tests. Done means the selected failures are resolved and the corresponding progress items are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100