ci: cap the compat profile job at 25 minutes - #13
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
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.
Cap the
compat.ymlprofilejob at 25 minutes.Why
That job hangs on GitHub runners - observed on several repos in the 0.1.6-alpha.2 batch (17 min to 1.5 h with no output, then passing in under a minute after
gh run cancel+rerun). It is a runner/task-side hang, not repo code. Without a cap the job occupies the 6-hour default, keeps the PRBLOCKED, and burns a runner the whole time.What
compat.yml: theprofilejob getstimeout-minutes: 25(its normal duration is about a minute, so the cap only ever fires on a hang).Verified locally
compat.ymlparses (js-yaml); the diff is one added line inside theprofilejob.