ci: make the Dylint lint step the required aggregate; drop the sentinel job - #375
Merged
Merged
Conversation
…el job The dylint-coverage job did ~3 s of work but waited for a runner after Dylint finished: 37 s (#369), ~1.5 min (#370), 1m53s (main 36520421024), 2m52s (PR #374, 36522485518, ~40% of that run's time to green). With one non-matrix Dylint job that has no if:, #363's aggregate holds in the job itself: its lint step fails when any lane fails and asserts the workspace pass ran. linux reports its own check. Full mode's full-coverage sentinel is unchanged.
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 dylint-coverage job did ~3 s of work but waited for a runner after
Dylint finished: 37 s (#369), ~1.5 min (#370), 1m53s (main 36520421024),
2m52s (PR #374, 36522485518, ~40% of that run's time to green).
With one non-matrix Dylint job that has no if:, #363's aggregate holds in
the job itself: its lint step fails when any lane fails and asserts the
workspace pass ran. linux reports its own check. Full mode's
full-coverage sentinel is unchanged.