feat: add timeouts - #1367
Open
sgaist wants to merge 7 commits into
Open
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
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.
Summary
Add timeouts to all workflows
This is an initial proposition to open the discussion. I don't claim these values to be the best so feel free to suggest others.
Use Cases
Avoid burning resources if something goes wrong and get quicker feedback.
As an example, on this day (20.08.2026), the lint workflow has had issues several times for the Python buildpacks and rather than fail quickly (it is supposed to have a timeout of 3 minutes), it ran anywhere from 10 minutes to more than an hour for no clear reasons.
While having timeouts will not fix the underlying issue, it will avoid burning runner resources.
Checklist