QA » openQA Project » openQA Tests

--
assert_and_click "vlc-playlist-empty";
send_key "ctrl-n";
assert_screen "vlc-network-window";
send_key "backspace";

--
vlc-playlist-empty shows up, so send_key "ctrl-n" is not working as I can say atm.

Please keep in mind that this is a "sporadic" issue. In the past you showed not having that much fun with sporadic issues so maybe not the most fun ticket for you to work on :) If you want to continue I however suggest to follow – as usual – https://progress.opensuse.org/projects/openqatests/wiki/Wiki#Statistical-investigation and properly test any potential fix also on aarch64 which can show differing behaviour.

100 test runt, no failure:

http://f40.suse.de/tests/7043#next_previous looks good with repeat 3 times and increase timeout for matching 'vlc-network-window'.

Only 1 failure is related to test module opensuse_welcome.

to check later:

https://openqa.opensuse.org/tests/1177828#live

https://openqa.opensuse.org/tests/1177908#step/vlc/23 shows already problem with ctrl-l to get vls-playlist-empty, this is performance issue.

to check: https://openqa.opensuse.org/tests/1178287

to check https://openqa.opensuse.org/tests/1179313#live

with code changes:

send_key_until_needlematch("vlc-playlist-empty", "ctrl-l", 3, 60);
send_key_until_needlematch("vlc-network-window", "ctrl-n", 3, 60);

to check https://openqa.opensuse.org/tests/1179314#next_previous

I don't think this worth to spend even more time on such sporadic issue which mostly related to performance issue. And we have open ticket regarding performance or typing issue for aarch64. If someone has a better idea to fix without fix the root cause, please go ahead.

zluo wrote:

I don't think this worth to spend even more time on such sporadic issue which mostly related to performance issue

Ok but as I suggest the same approach for all "[sporadic]" tickets I suggest you then apply the decision to all tickets, i.e. not pick any tickets about sporadic issues then.

And we have open ticket regarding performance or typing issue for aarch64.

aarch64 has not been mentioned in this ticket at all AFAIK. Also most likely we only have these tickets about the OSD arm workers.