Keep the release test matrix within each CI job budget - #20
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
1 participant
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 release CI runs five search configurations serially in one ten-minute job. Run 34288367658 passed Clippy and completed several test configurations, but the combined build/test job hit its timeout before the remaining configurations finished. The full-scan regression took over a minute in each completed configuration.
Run the five build/test configurations as independent matrix jobs. Each retains its ten-minute limit, existing fast-tier exclusions and full-scan assertions. The composed feature-precedence check remains included; publishing still requires all matrix jobs and Clippy. No Rust code, features or package version changes.
Validation: parsed both workflows and compared all five expanded test commands, skip filters, timeout and publish dependencies against the prior workflow; they are unchanged. Remote matrix jobs provide the actual runner verification. This is the single follow-up PR after #19 was merged and is needed to unblock the 0.0.14 publication pipeline.