action #41030
closed
[qam] test fails in updates_packagekit_kde - zypper update requires additional install step
Added by pcervinka over 5 years ago.
Updated over 5 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario opensuse-15.0-DVD-Updates-x86_64-install_with_updates_kde@uefi-2G fails in
updates_packagekit_kde
Reproducible¶
Fails since (at least) Build 20180913-1
Expected result¶
Last good: 20180912-4 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updates contain zypper update, incident 8725. Update will install zypper first, than it tries to install the rest.
Code in updates_available-tray is not designed for this case.
I will try to implement fix.
- Subject changed from [qam] test fails in updates_packagekit_kde to [qam] test fails in updates_packagekit_kde - zypper update requires additional install step
We had successful runs with this PR merged.
- Status changed from In Progress to Feedback
Wait few for more days to see, if there is no side effect. I will also try to recheck soft-failed bugs in updates_packagekit_kde, there seems to be no progress on them. Maybe it is time to revise the code of the test(from the long term point of view).
- Related to action #41396: [qam] Revise updates_packagekit_kde added
- Status changed from Feedback to Resolved
Seems to be after several ooo runs.
- Project changed from openQA Tests to 46
- Category deleted (
Bugs in existing tests)
- Target version changed from 445 to 457
- Project changed from 46 to openQA Tests
- Category set to Bugs in existing tests
- Target version deleted (
457)
not quite sure why you still do this but moving the tickets into a private subproject will hide it and this makes a problem, especially for "openSUSE only" tickets. Did you consider using maybe the top-level public QA project?
To track work in particular team where the work was done.
That's what I assumed but I do not understand how you "track work" which would restrict you to a single project. As I suggested, why not use the top-level public QA project?
Also available in: Atom
PDF