master: add queue timeout #343
Merged
Conversation
This file contains 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
LAVA jobs can get stuck for weeks if the priority isn't set properly which makes it pointless running those jobs after a week/month when the artefacts isn't available anymore or when its to late (someone else already done it)to report a bug. Another aspect is that LAVA eat up a lot of time just parsing the queue to find the next job to schedule. By adding a LAVA queue timeout to the job so it gets canceled if not scheduled in time, makes the queue length manageable. Signed-off-by: Anders Roxell <[email protected]>
|
Maybe I am being blind but where is |
I'm not sure that there is, but it works if you add it under the overall "timeouts:". W should probably update the LAVA docs. |
|
Agreed, we should get it added to LAVA docs. Ack, LGTM |
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.
LAVA jobs can get stuck for weeks if the priority isn't set properly which makes it pointless running those jobs after a week/month when the artefacts isn't available anymore or when its to late (someone else already done it)to report a bug. Another aspect is that LAVA eat up a lot of time just parsing the queue to find the next job to schedule. By adding a LAVA queue timeout to the job so it gets canceled if not scheduled in time, makes the queue length manageable.