ci: stop the merge gatekeeper waiting on Graphite's mergeability check - #14959
Open
asaf-sw wants to merge 1 commit into
Open
ci: stop the merge gatekeeper waiting on Graphite's mergeability check#14959asaf-sw wants to merge 1 commit into
asaf-sw wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Stops the merge gatekeeper timing out on every stacked PR. The cause is
Graphite / mergeability_check, which never completes while a PR's base is another open PR, so the gate waits out its full hour and dies reporting zero failed jobs.Detailed Summary for AI Bots
Problem
It self-resolves as the stack merges bottom-up, which is worse than a hard failure: it trains reviewers to ignore a red gate.
Root cause
Diffing the gate's own "All jobs" and "Completed jobs" groups across all 120 polls of run 31624863250 leaves exactly one job that never completes:
The correlation with base branch is exact: #14938 and #14946 (base
main) pass; #14944, #14947 and #14948 (stacked) time out. Skipped checks were a red herring, since #14944 and #14947 had zero skips.Change
Add
Graphite / mergeability_checkto the gate'signoredlist on the pull_request step. It is a stack-state indicator, not a CI signal about the code, and the list already ignorescode-review/reviewablefor the same reason. The merge_group step is untouched, since Graphite does not post this check against a merge queue ref.Name matching is substring-based, as the single
build_docker_imagesentry covering all three matrix variants shows.