DEV: bump timeout for non-scheduled builds #924
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
The most recent build timed out at 30 minutes. Bump timeout temporarily to get a gauge on how long self-hosted builds take (push to Dockerhub looks to be slower than Github-hosted runners).
fitzy101
force-pushed
the
fitzy/bump-timeout
branch
from
1174184 to
6926d55
Compare
|
The successful https://github.com/discourse/discourse_docker/actions/runs/12940557907/job/36095025663 So it looks like we just exceeded the 30min timeout |
tgxworld
approved these changes
Jan 24, 2025
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.
The most recent build timed out at 30 minutes. Bump timeout temporarily to get a gauge on how long self-hosted builds take (push to Dockerhub looks to be slower than Github-hosted runners).