Repository navigation
fix(ci): give Tests its own concurrency group (Build & Push gate is missing) - #161
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
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.
What
Build & Pushonmainhas been failing since the #155 merge: the run has one job (build: skipped) and notestsjob at all, so the image publish had no gate behind it. A known-good run had three nested jobs (tests / unit,tests / docker,tests / e2e).This gives
Testsits own concurrency group so it cannot collide withBuild & Pushon the same ref, and dropsTests' ownpush: [main]trigger (on main it should run once, as the jobbuildgates on).Honest status: I have not yet proven this fixes it — the failure only reproduces on a
mainpush, andTestshas noworkflow_dispatchtrigger so it cannot be fired in isolation. #160 tried a different theory and did not help. If this PR's ownTestsrun is green butmainstill showsbuild: skippedafter merge, the cause is elsewhere and I will revert rather than keep stacking experiments.