perf(ci): move webkit VR shards to Depot runners to fix timeout flakiness#60235
Merged
Conversation
Webkit page.goto timeouts persist at 5-9% on shared GitHub Actions runners due to CPU/memory contention (56+ consecutive days, 312+ occurrences). This scoped change moves only the 4 webkit shards to Depot dedicated runners (~75 vCPU-hours/day) while keeping the 16 chromium shards on ubuntu-latest to minimize cost impact. Addresses cost concerns raised in #56327 by limiting Depot usage to the browser with the actual flakiness problem.
mendral-app
Bot
changed the title
Contributor
|
Reviews (1): Last reviewed commit: "perf(ci): move webkit VR shards to depot..." | Re-trigger Greptile |
gantoine
approved these changes
May 27, 2026
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
2 participants
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
depot-ubuntu-latestrunners, keeping all 16 chromium shards onubuntu-latestpage.goto30s timeout flakiness (5-9% daily failure rate, 56+ consecutive days, 312+ occurrences)Context
Webkit page.goto timeouts have been failing at 5-9% daily on GitHub Actions shared runners since April 2. Yesterday spiked to 9.13%. PR #56327 (full Depot migration) has been blocked 23 days by unresolved cost review.
This PR is a scoped-down alternative that targets only the browser with the actual flakiness problem (webkit), minimizing cost while eliminating the reliability issue.
Related: #56327, Insight
Change
Webkit shards only run on master pushes (not PRs), so this change has zero cost impact on PR CI runs.
Note
Created by Mendral. Tag @mendral-app with feedback or questions.