Reduce Kythe workflow resource requests#11490
Merged
dan-stowell merged 1 commit intomasterfrom Mar 4, 2026
Merged
Conversation
The Generate Kythe Annotations workflow in dev has been getting stuck queued rather than running. After scoping the Kythe build to //proto/..., the previous 24 CPU / 60GB memory request looks oversized and may no longer match available dev executors. Lower the request to 8 CPU / 16GB while keeping 100GB disk so the action is more likely to schedule, without immediately increasing disk risk.
tylerwilliams
approved these changes
Mar 4, 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
2 participants
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 Generate Kythe Annotations workflow in dev has been getting stuck queued rather than running. After scoping the Kythe build to //proto/..., the previous 24 CPU / 60GB memory request looks oversized and may no longer match available dev executors. Lower the request to 8 CPU / 16GB while keeping 100GB disk so the action is more likely to schedule, without immediately increasing disk risk.