action #57704
closed[qam] [yellow] random test fails in yast2_apparmor - timeout is hit
100%
Description
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-Updates-x86_64-mau-extratests-yast2ui-textmode@64bit fails in
yast2_apparmor
Test suite description¶
Run console tests against aggregated test repo
Reproducible¶
Fails since (at least) Build 20190930-1
Expected result¶
Last good: 20190929-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by slemke over 4 years ago
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8685
I did some checks as this one fails are kind of random and usually occur more in the SLES12 code stream,
and indeed it takes some extra time in this ones, it seems to install the extra needed packages and after
that it does some internal processing(which give a fast popup) and then it finally opens the 'enable/disable' screen.
This PR gives it some extra seconds to do that.
Updated by slemke over 4 years ago
- Status changed from New to In Progress
- Difficulty set to easy
Updated by coolo over 4 years ago
Now it's a reproducible failure :)
https://openqa.suse.de/tests/3480877#step/yast2_apparmor/16 - I didn't want to blindly create a needle
Updated by slemke over 4 years ago
Seems the test will need another timeout improvement:
In line 109 it send and 'alt-end' combination to to jump to the last entry on the profiles list, right after that 'alt-end' it asserts the screen, it's possibly in heawy load scenarios this is taking the screenshot before the 'end of profiles' list is printed.
So I will add a 2 seconds 'col-down' in between.
thanks for keeping a eye on it!
Updated by slemke over 4 years ago
This one will cover it: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8705
Thanks!
Updated by coolo over 4 years ago
Updated by slemke over 4 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Timeout issue is resolved.