Give the docs deploy room to finish - #40
Merged
Merged
Conversation
The deploy job waits on GitHub's Pages backend and does no work of its own, so nothing here bounds how long it takes. A 10 minute cap killed PR #39's deploy at 10m03s: the change was merged, every check was green, and the published page kept serving the old content with nothing to indicate why. Measured the same day on netclab.github.io, which runs the same shape of workflow: 8m04s, a cancellation at 10m00s, then 9m12s. The successful runs sit just under the cap that killed one, which is how this stays invisible until it is not. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
mbakalarski
added a commit
that referenced
this pull request
Aug 6, 2026
PR #40 raised the deploy job to 30 minutes and the very next deploy still failed at 10m10s. The cap that fired was the action's, not the job's: deploy-pages takes a `timeout` input, defaults it to 600000 ms, and polls until then. Two independent ten-minute limits, so raising one moved the failure by ten seconds. The consequence is worse than a red run. On timeout the action cancels the deployment, and the deployment is keyed by commit SHA -- so re-running that workflow creates a deployment for the same SHA, is handed the cancelled state, and fails in ten seconds with "Deployment cancelled." Observed exactly that. A merged docs change then cannot be published at all without a new commit, which is why this one exists. Set to 20 minutes, deliberately under the job's 30, so the action times out and reports instead of being killed mid-flight. Co-authored-by: Claude Opus 5 <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
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.
PR #39 merged with both checks green, and its docs change never reached the
published site.
https://netclab.dev/netclab-xp/install/still links to theReleases page.
The deploy job was cancelled at 10m03s against
timeout-minutes: 10:The job only waits on GitHub's Pages backend — it does no work this repository
controls — so a cap on it does not bound anything useful, it just discards a
deploy that would have succeeded. Raised to 30.
Measured the same day on
netclab.github.io, which runs the same shape ofworkflow: 8m04s, a cancellation at 10m00s, then 9m12s. The successful runs
sit just under the cap that killed one, which is why this looked fine until it
was not.
Merging this deploys the pending
install.mdfix along with it, since.github/workflows/docs.ymlis in the workflow's ownpathsfilter.🤖 Generated with Claude Code