Allow for optional jobs not interfering which benchmark completion #2342
+153
−10
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.
I see a problem with this;
If a benchmark request (req1) is marked as
completewhile it still has unfinished optional jobs, and a subsequent benchmark request (req2) is marked asin_progress, then any optional jobs belonging to req1 will be skipped.If this were implemented using a generic
is_optionalflag, those jobs would also be skipped, because the request would be consideredcompletebefore the optional jobs were ever picked up.The way I see to rectify this is to change how the dequeue query logic works for the ordering. Moreover
is_optionalis perhaps misleading as a term though I'm struggling to think of a better name. However I'd be interested to know your thoughts before doing so.For the ui should we just filter optional jobs out?