action #18092
open[opensuse] test fail because of unexpected update notifications
0%
Description
Observation¶
openQA test in scenario opensuse-42.3-NET-x86_64-xfce@64bit fails in
chromium
asserting 'generic-desktop' but the screen is showing an unexpected update notification
Reproducible¶
Fails since (at least) Build 0149 and probably not every time, depending on "timing" between applying the updates and new updates appearing in the update repo
Expected result¶
Last good: 0147 (or more recent)
Problem¶
[28 Mar 2017 11:24:36] <okurz> coolo: https://openqa.opensuse.org/tests/377928#step/chromium/24 is an update notification icon messing the assertion. can we disable notifications as we do the explicit updating in before?
[28 Mar 2017 11:50:19] <coolo> okurz: and about the chromium failure - these notifications destroy SLE maintenance tests often too. we just should stop releasing updates
[28 Mar 2017 11:52:10] <okurz> coolo: yeah, but same as for the btrfs maintenance, do one explicit step, then prevent it running in the background, doesn't make sense?
[28 Mar 2017 11:53:06] <coolo> okurz: this might be very desktop specific though
Further details¶
Always latest result in this scenario: latest
Updated by lnussel about 7 years ago
in the update step before it actually claims having installed all available updates. There are only test updates in the update channel. At the point in time where the X11 tests run there shouldn't be any updates left.
Updated by lnussel about 7 years ago
for debugging this a "stop at test chromium and wait for input" feature would be nice ..
Updated by okurz over 2 years ago
- Priority changed from Normal to Low
This ticket was set to "Normal" priority but was not updated within 730 days which is 2 times the period of the SLO for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Low".