fleettest: add per-target protocol passes (check30/check29)#969
Merged
Conversation
A target can list older "protocols" (e.g. [30, 29]) in the fleet config; each runs as an extra stdio-pipe pass with runtests --protocol=N, the fleet analogue of a workflow's check30/check29 steps. The passes reuse the same parsed RSYNC_EXPECT_SKIPPED list as the default pipe run and appear as protoNN columns in the report and --timing breakdown. Targets without the key run only the default protocol and show "-" there. The example config's ubuntu-2604 target (mirroring ubuntu-build.yml, which has check30/check29 steps) now sets protocols: [30, 29].
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.
A target can list older "protocols" (e.g. [30, 29]) in the fleet config; each runs as an extra stdio-pipe pass with runtests --protocol=N, the fleet analogue of a workflow's check30/check29 steps. The passes reuse the same parsed RSYNC_EXPECT_SKIPPED list as the default pipe run and appear as protoNN columns in the report and --timing breakdown. Targets without the key run only the default protocol and show "-" there.
The example config's ubuntu-2604 target (mirroring ubuntu-build.yml, which has check30/check29 steps) now sets protocols: [30, 29].