Repository navigation
Keep Order-period coverage within the existing MySQL shard limit - #1183
Merged
Merged
Conversation
|
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.



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.