action #125930
closed
[qem][qe-core]test fails in consoletest_finish, failed to unlock the desktop [may be caused by screen_saver?]
Added by rfan1 about 1 year ago.
Updated 12 months ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-15-SP3-Server-DVD-Updates-x86_64-qam-allpatterns@64bit fails in
consoletest_finish
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Default system config with all patterns enabled.
Due changes in autoyast profile size of HDD incerased to 40GB
Reproducible¶
Fails since (at least) Build 20230313-1
Expected result¶
Last good: 20230312-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Files
- Subject changed from [qem][qe-core]test fails in consoletest_finish to [qem][qe-core]test fails in consoletest_finish, failed to unlock the desktop [may be caused by screen_saver?]
ph03nix wrote:
https://openqa.suse.de/tests/10688785 is passing. Looks like a sporadic issue?
Yes, but it has failed several times in past few builds.
If it is caused by screen_saver, worth to fix it :)
- Status changed from New to Workable
- Assignee set to zluo
Just disabling screensaver should be not the solution, there should be test also for that.
AFAIR it was left like this to have "real use case", this setup showed also issues with X.
dzedro wrote:
Just disabling screensaver should be not the solution, there should be test also for that.
AFAIR it was left like this to have "real use case", this setup showed also issues with X.
Thanks, add @zcjia into the loop!
Do you have any suggestion?
Hi @rfan1, in your PR, you doesn't change the YAML used by "qam-allpatterns" test, why?
Sorry, I was looking at different PR.
Have you tried if disabling screensaver can help this test?
zcjia wrote:
Hi @rfan1, in your PR, you doesn't change the YAML used by "qam-allpatterns" test, why?
Sorry, I was looking at different PR.
Have you tried if disabling screensaver can help this test?
Not yet! and as @dzedro mentioned, it should not be a good solution to disabling the screensaver.
dzedro wrote:
Just disabling screensaver should be not the solution, there should be test also for that.
AFAIR it was left like this to have "real use case", this setup showed also issues with X.
Hi dzedro, I'm not fully understanding what you mean here.
The problem I see in the failed test is that: we can't make screensaver go away (the system did not freeze, and no problem with X11 server), we use send_key to the screensaver, but it seems that the keyboard focus is out of way.
- Has duplicate action #126284: [qe-core] test fails in consoletest_finish added
zcjia wrote:
dzedro wrote:
Just disabling screensaver should be not the solution, there should be test also for that.
AFAIR it was left like this to have "real use case", this setup showed also issues with X.
Hi dzedro, I'm not fully understanding what you mean here.
The problem I see in the failed test is that: we can't make screensaver go away (the system did not freeze, and no problem with X11 server), we use send_key to the screensaver, but it seems that the keyboard focus is out of way.
IMO "we can't make screensaver go away" because the test is broken, if customer could not make screensaver go away then it's bug.
We can turn off screensaver, but there should be test for it.
dzedro wrote:
IMO "we can't make screensaver go away" because the test is broken, if customer could not make screensaver go away then it's bug.
We can turn off screensaver, but there should be test for it.
First, a customer (or anyone) can easily make screensaver go away.
It is just difficult to implement it reliably in openQA. A user can make screensaver go away by hitting a key, or moving mouse, or use mouse to drag the screensaver.
Second, you are right, screensaver should be tested somewhere, but it should not block many other tests.
So I think disabling screensaver in the context of this bug is the right choice.
- Status changed from Workable to Feedback
- Assignee changed from zluo to dzedro
I would resolve the issue. But maybe for the future could be considered to create screensaver specific test and don't block multiple tests with screensaver.
- Status changed from Feedback to Resolved
Would like to resolve due to inactivity. In case you think we should have a follow-up, let's create a new ticket!
Also available in: Atom
PDF
