openQA Project (public) » openQA Tests (public)

Was not able to work on this one, un-assign myself to give a chance to the team.

We trigger this test in a lot of scenarios. In general key press is lost and step is not asserted properly. Let's make failure obvious.

PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6388

Passed on OSD: https://openqa.suse.de/tests/2326130#step/yast2_snapper/58

please try again…

how is a SLE15SP1 test related to Leap upgrade failing?

Actually, it was not only opensuse problem, even in the description there is a test failed on Sle12.

But if referring to opensuse, passed test there: https://openqa.opensuse.org/tests/latest?test=update_Leap_42.3_kde%2Bsystem_performance&arch=x86_64&flavor=NET&version=15.1&machine=64bit-2G&distri=opensuse#step/yast2_snapper/55

Yes, but the ticket is "sporadic". Please see https://openqa.opensuse.org/tests/latest?test=update_Leap_42.3_kde%2Bsystem_performance&arch=x86_64&flavor=NET&version=15.1&machine=64bit-2G&distri=opensuse#next_previous and you are able to find yast2_snapper failing e.g. in the job before the last one. I don't see how a single verification run can suffice. Could you either trigger some more tests to verify with statistics or just keep it open until we had more builds that show stable behaviour? If you prefer to open another ticket, ok as well, you can go ahead.
If you prefer to talk about the ticket or how we handle it in a different communication channel I am happy to do so, e.g. in person.

As discussed, okurz has proposal to make job soft-fails when issue is detected. riafarov proposes running test module in separate test suite.

blocked by #39719

Seems that issue is gone for now. However, we should consider changing scenario to have changes we can predict. For example doing one snapshot, changing single directory and check diff, instead of using unpredictable diff of currently created snapshot and the one which was there before.