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.
Close #6329
In the example of 6329 an upstream failure generates a bunch of partially satisfied tasks - i.e. active (
n=0
) but not queued. Triggering them manually causes them to be added to aforced_released
list - wrongly as they were not queued in the first place.A bit later, the
forced_released
tasks top up the list of naturally released tasks. But by then there is some overlap between the two lists, so the queue limit matters (along with some task-state related race condition which I haven't fully understood, but that doesn't matter) as to how many of these tasks end up getting submitted again.Check List
CONTRIBUTING.md
and added my name as a Code Contributor.setup.cfg
(andconda-environment.yml
if present).?.?.x
branch.