Skip to content

Keep Order-period coverage within the existing MySQL shard limit - #1183

Merged
rmcdaniel merged 1 commit into
mainfrom
fix/1182-covered-order-shard
Nov 17, 2026
Merged

rmcdaniel merged 1 commit into
mainfrom
fix/1182-covered-order-shard

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

The first complete main build after #1182 reached the existing MySQL 20-minute limit. Its event trace records all 17 Order-period cases passed before the shard reached the existing timeout-cleanup tests; 140 tests passed and two backend cases skipped, but the combined shard did not finish and produced no complete JUnit/coverage report. The original run remains failed.

The new class had a non-coverage MySQL duration in the covered timing profile. Reserve its own shard with a conservative 1,200-second scheduling weight, derived from the completed-class upper bound in that combined run. This is not a measured per-class duration and does not extend any deadline. The other 219 weights, complete test inventory, all 16 coverage shards, workflow commands and coverage gates remain unchanged. PostgreSQL allocation is unchanged.

Validation: the existing shard verifier passes; all 220 feature files remain represented exactly once across each backend. The generated MySQL plan contains only the Order-period class in shard 0. All source, tests, workflow and coverage-contract bytes equal main; its completed unit and PostgreSQL results are retained, while the fresh required pipeline validates this scheduling correction.

Refs #1069, #1182.

@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel
rmcdaniel merged commit 9a6c8cb into main Nov 17, 2026
32 checks passed
@rmcdaniel
rmcdaniel deleted the fix/1182-covered-order-shard branch November 17, 2026 06:58
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