action #80686
closedwrong label carry-over to a job where an additional module failed before the one failing in before
Description
Observation¶
https://openqa.opensuse.org/tests/1491970#next_previous shows https://openqa.opensuse.org/tests/1491125 which failed in "gnome_music" and was marked with https://bugzilla.opensuse.org/show_bug.cgi?id=1178555 . The next job in the scenario is https://openqa.opensuse.org/tests/1491970 which failed in "zypper_clear_repos" and then "gnome_music", so different modules and even one before "gnome_music". But still the bug https://bugzilla.opensuse.org/show_bug.cgi?id=1178555 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
Suggestions¶
- The logs from https://openqa.opensuse.org/tests/1491970 are likely still available on o3 webUI right now if you hurry to look into :)
Updated by mkittler almost 3 years 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 https://github.com/os-autoinst/openQA/pull/3988 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.
Updated by mkittler almost 3 years ago
- Related to action #94880: Carry-over despite mismatch of failing job modules added
Updated by mkittler almost 3 years ago
- Status changed from New to Feedback
PR https://github.com/os-autoinst/openQA/pull/3988 has been merged.
Updated by mkittler almost 3 years ago
- Status changed from Feedback to Resolved
I'm marking this as resolved because https://github.com/os-autoinst/openQA/pull/3988 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.
Updated by okurz almost 3 years ago
- Target version changed from future to Ready
thank you. Good call!