Repository navigation
ci: fix E2E shard re-runs and stop using the stale RPC key - #995
Merged
Merged
Conversation
Re-running failed jobs carries a successful E2E Build into the new attempt without uploading again. The shards waited 15 minutes for an artifact named after the new attempt and then failed. A finished build now means the newest upload in the run. A running build still uploads under the current attempt, so shards take it as soon as it lands. 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.
|
With TEMPO_RPC_API_KEY configured, live tests route Moderato reads through the keyed relay. Those reads stay stale after a transaction: receipts never confirm and balances stay at 0. Four live tests failed on GitHub-hosted runners (pay-with-ousd-fees, manage-stablecoin, mint-stablecoins, faucet passkey). Live tests use the anonymous RPC again until the relay serves fresh reads. The secret stays configured. Co-Authored-By: Liam Horne <[email protected]> Co-Authored-By: Claude Opus 5.5 <[email protected]>
snario
changed the title
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
Two CI fixes.
main's E2E check is red until this merges.1. Live tests stop using
TEMPO_RPC_API_KEYThe key was configured today, which turned on #984's authenticated path: live tests send Moderato reads through
rpc.moderato.tempo.xyz/<key>. On GitHub-hosted runners, reads through that keyed relay stayed stale after transactions:pay-with-ousd-fees: "Timed out while waiting for transaction … to be confirmed."faucet(connected passkey wallet): balances stayed0after funding.manage-stablecoinandmint-stablecoinsalso failed.The same tests pass on the anonymous RPC, so the Playwright step no longer receives the key. The secret stays set. The relay needs to serve fresh reads before the key is passed again and the shards move to Depot (#994).
2. Re-running failed shards finds the E2E build
Re-run failed jobs carries a successful E2E Build into the new attempt without uploading again. The shards waited for
e2e-dist-<new attempt>, timed out after 15 minutes, and failed without testing (run 38610201946, attempt 2).e2e-dist-*artifact in the run.e2e-dist-<current attempt>as soon as it lands.Against the run that hung, the script finds
e2e-dist-1in 1.4s.Co-Authored-By: Liam Horne [email protected]
🤖 Generated with Claude Code
Prompted by: Liam