Skip to content

chore(ci): refresh integration shard weights from the latest staging validation - #10260

Open
waleedlatif1 wants to merge 2 commits into
stagingfrom
ci/refresh-integration-durations
Open

waleedlatif1 wants to merge 2 commits into
stagingfrom
ci/refresh-integration-durations

Conversation

@waleedlatif1

@waleedlatif1 waleedlatif1 commented Nov 20, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • Regenerated vitest.integration-durations.json with scripts/update-integration-durations.ts from three staging validation runs (60 integration reports, 399 files). The committed weights were three weeks old
  • These weights decide how DurationBalancedSequencer packs integration files into the 8 shards. Stale weights only affect balance, never what runs

Weights 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):

scored on old weights three-run weights
this PR's first run 337s / 213s 315s / 214s
staging validation 44815408851 328s / 211s 267s / 239s

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 through document_pkey instead 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

  • Improvement

Testing

  • Generated by the repo's own script; out-of-sample comparison above; full CI on this PR

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing (new tests pass the test-audit authoring gate)
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@vercel

vercel Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
docs Ignored Ignored Preview Nov 20, 2026 11:38pm UTC

Request Review

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Turn on auto-fix | Re-trigger cubic

@greptile-apps

greptile-apps Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] This timing-only refresh appears safe to merge.

Summary

Refreshes vitest.integration-durations.json with newer integration-test timings and weights for recently added suites.

  • Integration tests use refreshed timing estimates to choose their CI shards.

Reviews (1) · Last reviewed commit: "chore(ci): refresh integration shard wei..." · Reviewed by Greptile

This branch was successfully deployed

1 active (outdated) deployment
Preview — 9a0a2272 Deployed Nov 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant