fix(ci): make Playwright apt retries recover - #19133
Merged
Merged
Conversation
![ai-sdk-factory[bot]](https://avatars.githubusercontent.com/in/4315504?s=60&v=4){kind=small}
gr2m
enabled auto-merge (squash)
August 19, 2026 22:31
This was referenced Aug 19, 2026
gr2m
added a commit
that referenced
this pull request
Aug 19, 2026
## Background Backport of #19133 to the actively maintained v6 release branch. The RSC e2e Playwright dependency install could outlive the outer timeout, retain an apt lock, and make every retry fail immediately. ## Summary - bound apt download retries and network timeouts - wait for all apt/dpkg lock files before every attempt - run the Playwright dependency install as root in its own process group so timeout cleanup reaches apt descendants - run RSC e2e when its workflow definition changes ## Validation - the main PR completed the full CI matrix successfully, including Test RSC e2e - pnpm check - pnpm type-check:full - workflow YAML parse and RSC shell syntax checks No changeset: this only changes CI infrastructure.
gr2m
added a commit
that referenced
this pull request
Aug 19, 2026
## Background Backport of #19133 to the actively maintained v5 release branch. The linked v5 RSC e2e failure showed the Playwright dependency install outliving the outer timeout, retaining an apt lock, and making every retry fail immediately. Failure: https://github.com/vercel/ai/actions/runs/32302334578/job/96228309554 ## Summary - bound apt download retries and network timeouts - wait for all apt/dpkg lock files before every attempt - run the Playwright dependency install as root in its own process group so timeout cleanup reaches apt descendants - run RSC e2e when its workflow definition changes ## Validation - the main PR completed the full CI matrix successfully, including Test RSC e2e - pnpm check - workflow YAML parse and RSC shell syntax checks - pnpm type-check:full was run; release-v5.0 currently reports unrelated React type-resolution errors across examples, while this diff only changes .github/workflows/ci.yml No changeset: this only changes CI infrastructure.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
The Test RSC e2e job failed three times on August 19 while Playwright installed Chromium system dependencies:
In each run, apt-get update stalled against azure.archive.ubuntu.com until the 15-minute timeout. Playwright had spawned apt-get through a nested sudo process, so apt-get survived the timeout and retained /var/lib/apt/lists/lock. The retry guard only watched /var/lib/dpkg/lock-frontend, causing attempts two and three to fail immediately.
This matches the active GitHub runner-images incident: actions/runner-images#14594
Summary
End-to-End Verification
This is a CI-only change. The intermittent mirror timeout cannot be forced locally; this pull request CI exercises the normal Test RSC e2e path. The timeout path now keeps the Playwright process and its privileged apt descendants in one process group and checks the exact lock observed in all three failures before retrying.
Validation
Checklist
Related Issues