action #80686

wrong label carry-over to a job where an additional module failed before the one failing in before

Added by okurz 8 months ago. Updated 23 days ago.

Concrete Bugs
Target version:
Start date:
Due date:
% Done:


Estimated time:


Observation shows which failed in "gnome_music" and was marked with . The next job in the scenario is which failed in "zypper_clear_repos" and then "gnome_music", so different modules and even one before "gnome_music". But still the bug was carried over which is unexpected.
The problem in "zypper_clear_repos" might have been missed as the job is automatically labelled with a bug that only applies to "gnome_music".

Acceptance criteria

  • AC1: No carry-over happening when a new module fails in before the original one


Related issues

Related to openQA Project - action #94880: Carry-over despite mismatch of failing job modulesResolved2021-06-29


#1 Updated by mkittler 29 days ago

  • Status changed from Workable to New
  • Assignee set to mkittler

With all referenced jobs cleaned up this ticket is not workable. However, I created #94880 yesterday which is likely about the same problem (but with more recent jobs). The the PR likely fixes the issue - although it is hard to tell what the exact issue was at this point.

I would therefore just consider this ticket resolved as soon as #94880 is resolved.

#2 Updated by mkittler 29 days ago

  • Related to action #94880: Carry-over despite mismatch of failing job modules added

#3 Updated by mkittler 29 days ago

  • Status changed from New to Feedback

#4 Updated by mkittler 23 days ago

  • Status changed from Feedback to Resolved

I'm marking this as resolved because fixes problems with the carry-over and at this point it is not possible to figure out what specific problem this issue is about because all referenced jobs have already been cleaned up.

#5 Updated by okurz 23 days ago

  • Target version changed from future to Ready

thank you. Good call!

Also available in: Atom PDF