ci: shard tracer-release system tests four ways - #4143
Draft
bm1549 wants to merge 1 commit into
Draft
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.
Description
Each of the 25 tracer-release system-test definitions currently runs its scenario list serially. This adds native
parallel: 4, producing 100 execution lanes. A checked-in selector sorts and deduplicates the canonical scenario set, then assigns disjoint round-robin slices using GitLab's 1-based node index.One system-tests SHA is resolved in
prepare code, published as a dotenv artifact, and checked out exactly by every shard. Required Python and PHP tests cover selector behavior, exact-once coverage, the shared pin, and all 25 generated job definitions. Valgrind is unchanged.Current producer output splits 96 scenario executions into
[24, 24, 24, 24]. Scenario-phase wall clock can approach one quarter of the current time; setup and weblog build work are repeated, and the slowest shard still sets wall clock.Draft integration note: merge this after #4144 and #4142, then rebase. During conflict resolution, keep the fixed source/image pair from #4144, retain the shard selector, add producer-level
PARAMETRICexclusion, and remove the redundant unsharded extractor path.Tested with:
git diff --checkReviewer checklist