Prevent workflows running longer than 5 hours #59
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
There seems to be a bug where cancelling a workflow doesn't take down the runner. In general 3 days is a long time to leave something idle, so let's be a bit more aggressive about shutting them down while we work on fixing the bug
Collaborator
Contributor
Author
|
Thanks for letting me know! Somehow we ended up with 10 idle workers and no actions running and the main thing that's changed recently is that we started cancelling stale runs after new pushes. I'll try to repro and investigate on monday. |
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There seems to be a bug where cancelling a workflow doesn't take down the runner. In general 3 days is a long time to leave something idle, so let's be a bit more aggressive about shutting them down while we work on fixing the bug.
(Edit: sorry, wrong org)