Aborted and Failed work requests are shown when a second work request is successful

I'm filling as a bug report, but it could be a feature request as well (leaving for debusine developers to choose which tag to use).

Describe the bug

I've uploaded gdk-pixbuf yesterday (workflow 197302) and some jobs were aborted for no apparent reason (in #1081 it was pointed out that might be some workers being updated) and new work requests were issued and succeeded, but the aborted ones were still shown.

The same is true for a failed autopkgtest from a rdep (ibus), it only failed on arm, so my assumption was some hiccup during the test, so I re-triggered and it passed. But the failed test still show up in the workflow.

My expectation was only the success is shown in these cases were for some reason the initial work request fail (or is aborted) and a retry is successful (this is the behavior GitLab CI has - maybe I'm just biased by it).

The actual status of the parent work request is updated accordingly as shown in the ibus case, but the failed work request is shown in the workflow.

How to reproduce the bug

Not sure if it can be easily reproduced.