fix(ci): point the deploy check gate at the sharded test_distributed checks#8088
Merged
Merged
Conversation
phacops
approved these changes
Jun 22, 2026
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.
The deploy pipeline's GitHub-checks gate (
gocd/templates/bash/check-github.sh) waits up to 60 minutes for a check namedTests and code coverage (test_distributed). Sharding that job (#8067) renamed it to(test_distributed, 0, 2)and(test_distributed, 1, 2), so the old name never reports and the gate hangs, blocking deploys. We point the gate at the two sharded checks instead. Same fix we made to the merge ruleset; this was the second hardcoded consumer of the old name.