Learn more about these different git repos.
Other Git URLs
I removed build #616126 but it's build product, including RPMs and repodata are still present, even quite a while (many tens of minutes if not several hours) after the build deletion.
Even if this is just some kind of delayed action, the delay needs to be much shorter. A person could be deleting an erroneous build and need that action to be effected right away so that users don't pull an erroneous package.
This happens if the action queue is stuck. The delay is usually short but it gets longer if there is a problem with processing a certain action task. We could make the action execution parallel.
Metadata Update from @msuchy: - Issue tagged with: RFE
We could make the action execution parallel.
+1
Alternatively, we can catch all exceptions from handle_foo methods on some top-level and add some mechanism, that when an action fails, it is going to be put on the end of the queue. This way one bad action can't stuck the whole queue and also will be eventually processed again.
handle_foo
The only positive feature of the current situation is that we can easily notice, that some action doesn't work, because the queue is stuck and therefore nothing works. In case of the parallel actions or circular queue, we don't notice stuck action that simply. However, with proper logging or some sort of monitoring it should be alright.
Metadata Update from @praiskup: - Issue assigned to praiskup
Commit 89530f4 fixes this issue
Login to comment on this ticket.