New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Staging list --supersede -> results in weird issues #8994
Comments
The easiest workaround to recover is to delete adi:11 completely and have a new adi be re-setup. I did not do that yet, in case somebody wants to look into more metadata of the proj which would vanish when I delete it |
sbot killed the by_project review before trying to unstaging it:
That case noone thought of I'd say. |
Ping - this issue causes staging bot to grind to a halt quite frequently. |
Just worked around this for sr 781222 by reopening it, unselecting and declining again. |
The workaround is merged. |
Well the requests auto-declined by bots are still a challenge. I have to use something like this construct otherwise I'll not hit the < 5 sec window of auto-decline done by licensedigger. This is quite painful and annoying tbh.
Normal worfklow would result into failure
|
what @lkocman meant was: I am not using the factory plugin so I don't benefit from the workaround 😃 |
That DOES look like using the staging plugin (otoh, unselect in combination with -m implies 'unselect and add to ignore' - which is really not what you want to do when unselecting a declined request) |
@lkocman >
why do you reopen it? you can unselect a declined request (OBS internally reopens, unselects, declines) |
That works neither for me nor @lkocman |
Correct, this is why I did the re-open |
Ah - you are not target maintainers - that must be the difference there (Staging manager role seems to be not sufficient - which is indeed an issue then) |
I somewhat think what I observe could be a regression from
#8946 probably together with a racing condition between when an SR is incoming and the execution order / runtime of the staging bot
'd observed it at least twice now - latest case this morning.
gambas3 (sr#766204) was staged in adi:11; a newer submission was incoming for the same package (sr#766549 at 10:20).
at 10:23, the package old package was decline by sbot (list --supersede). Which should then replace the package in adi:11 with the new one.
Looks all right, but at the same time tbe bot crashed with:
The result now is that adi:11 still has 766204/gambas 3 tracked (state declined), but the package container in adi:11 no longer exists (package was unstaged according to the history)
Since 766204 is still tracked though, without a package being present, it is not possible to unstage it anymore - and a future run of staging list --supersede results in
The text was updated successfully, but these errors were encountered: