Move leeway vet to validate #12999
Merged
Move leeway vet to validate #12999
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
mads-hartmann
force-pushed
the
mads/move-leeway-vet-to-validate
branch
from
552bc7b to
41d6ad6
Compare
mads-hartmann
force-pushed
the
mads/move-leeway-vet-to-validate
branch
from
41d6ad6 to
7dc93e2
Compare
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
This follows up on #12998 and adds
leeway vetto the Validating changes phase too to catch such issues early on.It also means we save 7 seconds as this was otherwise running sequentially as part of the build
Related Issue(s)
No issue, just feeling like doing some minor cleanups.
How to test
Release Notes
Documentation
N/A
Werft options: