action #34921
closed
[sle][functional][u][sporadic][medium] gnome desktop runner does not appear in gnome_control_center test
Added by mloviska about 6 years ago.
Updated almost 6 years ago.
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 17
Description
In previous tests (xterm,sshxterm,updates_packagekit_gpk) gnome desktop runner works as expected.
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-x86_64-default@64bit-smp fails in
gnome_control_center
Reproducible¶
Fails since (at least) Build 0236 (current job)
Expected result¶
Last good: 0235 (or more recent)
Further details¶
Always latest result in this scenario: latest
- Subject changed from [sle][functional] gnome desktop runner does not appear in gnome_control_center test to [sle][functional][u] gnome desktop runner does not appear in gnome_control_center test
- Due date set to 2018-06-19
- Target version set to Milestone 17
- Due date deleted (
2018-06-19)
- Due date set to 2018-07-03
please crosscheck current results and do not invest too much time on this ticket
- Subject changed from [sle][functional][u] gnome desktop runner does not appear in gnome_control_center test to [sle][functional][u][sporadic] gnome desktop runner does not appear in gnome_control_center test
- Target version changed from Milestone 17 to Milestone 17
- Status changed from New to Workable
- Subject changed from [sle][functional][u][sporadic] gnome desktop runner does not appear in gnome_control_center test to [sle][functional][u][sporadic][medium] gnome desktop runner does not appear in gnome_control_center test
Ah true, I have not check the clock. Nice catch!
- Status changed from Workable to Rejected
- Assignee set to okurz
mloviska wrote:
Maybe it is enough to just monitor it for a while.
Thank you for checking.
Checking back from the most recent build 0266 I find 2/24 failures. To me it seems like we are hitting https://bugzilla.suse.com/show_bug.cgi?id=1063638 in the older builds which did not yet have an updated kernel 4.12 but still the old one 4.4 . I guess we do not need to do anything more for this ticket in particular. We have the mentioned bug as well as more tickets, e.g. to rework the force_cron_run test module, that should help already.
Also available in: Atom
PDF