test(proxied): cut shard-4 timeout — revert per-subtest project splits, move Ready to shard 8

The per-subtest project split multiplied bd init calls (each runs the full
migration chain on a fresh DB): epic 2->8, set-state 1->4, unclaim 2->9,
defer 1->7. That is added, not saved, wall-clock on already-saturated
shards and pushed shard 4/8 over the 15m budget. Revert those five suites
to one shared project per test function (the read-suite pattern), and move
the pre-existing heaviest suite (Ready: 36 subtests / 34 inits) off the
overloaded shard 4 onto the near-idle shard 8.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
coffeegoddd☕️✨ 2026-07-17 17:59:41 -07:00
commit 7caa8cd554
5 changed files with 105 additions and 162 deletions

View file

@ -25,7 +25,6 @@
8 3 TestProxiedServerGateList
8 3 TestProxiedServerPriority
8 4 TestProxiedServerReady
8 4 TestProxiedServerReopen
8 4 TestProxiedServerDeleteConcurrent
8 4 TestProxiedServerReadyWisp
@ -62,6 +61,7 @@
8 8 TestProxiedServerReopenConcurrent
8 8 TestProxiedServerDoltRemoteRemove
8 8 TestProxiedServerChildren
8 8 TestProxiedServerReady
# Parity-suite proxied tests (added with the cmd/bd embedded-parity port).
# Balanced by subtest count; shard 1 stays TestProxiedServerUpdate-only.