Budget the refresh job for a resubmitted compile attempt - #88
Merged
Conversation
The bootstrap script now resubmits a dead compile job once (core #379); each attempt polls up to 25 min, so 30 min no longer fits the worst case of a first attempt timing out plus a full second attempt.
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.
Companion to smaramwbc/statewave#379: the bootstrap script now resubmits a dead compile job once when a core deploy orphans it mid-run. Each attempt polls up to 25 minutes, so the job's
timeout-minutes: 30no longer covers the worst case (first attempt times out at 25 min, second attempt runs full length). Raised to 60 with the reasoning in the workflow comment.No behavior change when the first attempt succeeds — the job still finishes in the usual few minutes.