Repository navigation
chore(ci): refresh integration shard weights from the latest staging validation - #10260
Open
waleedlatif1 wants to merge 2 commits into
Open
waleedlatif1 wants to merge 2 commits into
waleedlatif1 wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
[Low impact] This timing-only refresh appears safe to merge. SummaryRefreshes
Reviews (1) · Last reviewed commit: "chore(ci): refresh integration shard wei..." · Reviewed by Greptile |
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
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
vitest.integration-durations.jsonwithscripts/update-integration-durations.tsfrom three staging validation runs (60 integration reports, 399 files). The committed weights were three weeks oldDurationBalancedSequencerpacks integration files into the 8 shards. Stale weights only affect balance, never what runsWeights from one run overfit it: per-file times vary between runs. Averaged over three runs, then scored with the sequencer's packing against held-out runs the weights never saw (apps/sim, slowest / fastest shard):
Over 97 recent PR runs the slowest apps/sim shard ran 325s at p50 and 439s at p90. On runs where the app build is a cache hit, the integration shards are the critical path.
The first run failed one shard on
listing-continuation.integration.ts("scans a dense window once…"): a plan check read 14,551 rows throughdocument_pkeyinstead of one window. It is unrelated to shard weights: the same test failed on a staging validation and on two other branches before this PR, and it passed five isolated local runs. It is tracked separately.Type of Change
Testing
Checklist
test-auditauthoring gate)