Repository navigation
Chore: add a timeout to every workflow job - #177
Merged
Merged
Conversation
Without timeout-minutes a hung job holds a runner for the 360-minute default. Each limit is set well above the job's observed runtime.
SandObserver
added
the
github_actions
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
timeout-minuteson all eleven runner jobs across the nine workflows: 15 fortestande2e, 20 foranalyzeandscan, 30 forbuild-and-push, 10 forrelease-page,docs-rebuild,prep,tag,validateandupdate.release.yml'se2ejob untouched; it callse2e.yml, whose job now carries the limit.Testing
All green, including the Docker smoke build. No new coverage; the change is workflow configuration only.
Checklist