CI Reliability 2026-08-28
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/76510 to node-test-pull-request/76605 that failed 2 or more PRs
(Generated with ncu-ci walk pr --stats=true --markdown reports/2026-08-28.md)
| UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
|---|---|---|---|---|---|---|
| 2026-08-28 02:43 | 6 | 12 | 8 | 14 | 60 | 15.00% |
Open https://github.com/nodejs/reliability/blob/main/reports/2026-08-28.md to see failure details
Progress
-
ERROR: Error fetching remote repo 'origin'(7) -
error: could not apply 61890720c8a... add readme and initial code(10) -
fatal: No rebase in progress?(6) -
fatal: no rebase in progress(6) -
Failed to trigger fanned build(4) -
Failed to trigger node-test-commit(3) -
Failed to trigger sub builds(3) -
error: could not apply a7909014f77... tls: implement tls.getCACertificates()(3) -
ERROR: Head was detached. Conflicts likely - checking out _jenkins_local_branch before starting(2) -
error: could not apply 7b6b21a8aae... doc: move histogram.burnRate to correct location in doc(2) -
parallel/test-watch-mode-files_watcher(14) -
parallel/test-fs-watch-recursive-delete-race(13) -
parallel/test-watch-mode-files_watcher-clear(13) -
sequential/test-fs-watch(13) -
parallel/test-fs-watch-recursive-delete(12) -
parallel/test-vfs-real-provider-watch(12) -
sequential/test-watch-mode-worker(12) -
parallel/test-fs-watch(11) -
parallel/test-fs-promises-watch(9) -
node-api/test_sea_addon/test(3) -
pummel/test-fs-watch-non-recursive(3) -
sea/test-single-executable-application(3) -
parallel/test-inspect-async-hook-setup-at-inspect(2) -
parallel/test-stream-pipeline-http2(2) -
sea/test-build-sea(2) -
sea/test-build-sea-executable-field(2) -
sea/test-single-executable-application-asset-keys(2) -
sea/test-single-executable-application-asset-keys-empty(2) -
sea/test-single-executable-application-assets(2) -
sea/test-single-executable-application-assets-raw(2) -
sea/test-single-executable-application-disable-experimental-sea-warning(2) -
sea/test-single-executable-application-empty(2) -
sea/test-single-executable-application-esm(2) -
sea/test-single-executable-application-esm-code-cache(2) -
sea/test-single-executable-application-exec-argv(2) -
sea/test-single-executable-application-exec-argv-empty(2) -
sea/test-single-executable-application-exec-argv-extension-cli(2) -
sea/test-single-executable-application-exec-argv-extension-env(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) -
sea/test-single-executable-application-snapshot(2) -
sea/test-single-executable-application-snapshot-and-code-cache(2) -
sea/test-single-executable-application-snapshot-worker(2) -
sea/test-single-executable-application-use-code-cache(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/2026-08-28.md and reproduce the generated view with ncu-ci walk pr --stats=true --markdown reports/2026-08-28.md; inspect the linked node-test-pull-request jobs and the repeated Git, watch-mode, and SEA failures. Done means the recurring failures are diagnosed and the relevant CI or test issues are resolved, with a later report showing improved reliability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100