Repository navigation
ci: build E2E once on Depot and test while shards set up - #988
Merged
Merged
Conversation
E2E shards each rebuilt the site on GitHub ARM runners (~5 minutes) before running ~85s of Playwright tests. - E2E Build compiles the site once on a Depot runner, about twice as fast for this single-threaded build, inside the shards' Playwright container so absolute paths in the server output still match. - The three required E2E shards stay on GitHub-hosted runners, install dependencies in parallel with the build, then wait for and download its artifact. Moderato limits RPC connections per IP, and Depot's shared egress IPs exhaust it for the live-transaction tests. - Sitemap builds on Depot too. Set DEPOT_DISABLED to fall back. - pnpm store cache falls back to the previous store on lockfile changes. - document-semantics checks every route's prerendered head and H1 in one request sweep and hydrates each section's landing and deepest page in the browser: 282 page loads become 40 tests (~42% of E2E test time). Co-Authored-By: Liam Horne <[email protected]> Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 14, 2026
This branch was successfully deployed
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.
Summary
Follow-up to #986 to get the E2E check under 5 minutes. After #986 each E2E shard still rebuilt the site on a GitHub ARM runner (~5 min) before ~85s of Playwright tests.
rootDir) match where shards serve it.e2e-distartifact (scripts/wait-for-e2e-build.mjs).429 too many connections from this IPto the browser from the first request on Depot, whose egress IPs are shared (Tempo's own CI runs there too). The two passkey + faucet live tests failed on every Depot attempt and pass on GitHub runners. fix(ci): authenticate live E2E RPC requests #984's authenticated RPC would fix this onceTEMPO_RPC_API_KEYis configured — it's currently empty in CI.ubuntu-latest).DEPOT_DISABLEDrepository variable totrueto fall back to GitHub runners.restore-keysfallback so a lockfile change reuses unchanged packages instead of a cold install.Fewer browser page loads, same coverage
document-semanticsmade 280 full browser loads (42% of all E2E test time) to check one title/H1/description/og:title/canonical per route. It now:Mutation-checked: injecting a second
<h1>into/docs/accountsfails the sweep with/docs/accounts: 2 h1.Expected timeline
E2E Build ≈ setup 25s + build ~2 min + upload ~10s; shards overlap their ~50s setup with it, then download (~15s) and test (~50s). Target: E2E checks complete in ~4 min. This PR's own CI run will confirm.
Co-Authored-By: Liam Horne [email protected]
🤖 Generated with Claude Code
Prompted by: Liam