Increase GitHub Pages deploy timeout to absorb queue backlog - #324
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
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.
Summary
The
deploy docsjob keeps timing out after 10 minutes. Digging into the deploy logs of run 31106667493 shows it isn't permanently stuck — it's slow:Current status: deployment_queued(GitHub Pages runner backlog before the build even starts)Current status: deployment_in_progress, still building when the action's 10-minute total timeout cancelled it →failureThe queue phase alone eats more than half the budget, so the actual Pages build never gets enough time to finish.
Changes
actions/deploy-pagessteptimeoutinput to1500000ms (25 min) — the action defaults to 10 min, which is too tight given the queue backlog.timeout-minutesto 30 and the jobtimeout-minutesto 40 so the longer deploy fits within the job budget.Notes
The
github-pagesenvironment (added earlier) is correct and remains. This PR only gives the deployment enough time to get through the queue and complete.