Project

General

Profile

action #60989

[qe-core][functional][opensuse] test fails in consoletest_finish - ensure_unlocked_desktop unreliable

Added by StefanBruens almost 2 years ago. Updated 23 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-NET-x86_64-xfce@64bit fails in
consoletest_finish

ensure_unlocked_desktop

  • unlocks (sucessfully)
  • starts the desktop runner ('alt-f2', successfully)
  • tries to close it again ('alt-f2') - fails

As a result, assert_screen(mustmatch='generic-desktop') fails.

Log excerpt:

[2019-12-12T17:50:04.403 CET] [debug] <<< testapi::send_key(key='alt-f2', do_wait=0, wait_screen_change=0)
[2019-12-12T17:50:04.738 CET] [debug] /var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/tests/console/consoletest_finish.pm:54 called x11utils::ensure_unlocked_desktop
[2019-12-12T17:50:04.738 CET] [debug] <<< testapi::check_screen(mustmatch='desktop-runner', timeout=30)
...
[2019-12-12T17:50:11.746 CET] [debug] no change: 22.9s
[2019-12-12T17:50:12.916 CET] [debug] >>> testapi::_handle_found_needle: found desktop-runner-xfce-20190822, similarity 1.00 @ 316/337
[2019-12-12T17:50:12.916 CET] [debug] /var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/tests/console/consoletest_finish.pm:54 called x11utils::ensure_unlocked_desktop
[2019-12-12T17:50:12.916 CET] [debug] <<< testapi::send_key(key='esc', wait_screen_change=0, do_wait=0)
[2019-12-12T17:50:13.185 CET] [debug] /var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/tests/console/consoletest_finish.pm:54 called x11utils::ensure_unlocked_desktop
[2019-12-12T17:50:13.185 CET] [debug] <<< testapi::assert_screen(mustmatch='generic-desktop', timeout=30)
...
[2019-12-12T17:50:44.433 CET] [debug] no match: -0.6s, best candidate: XFCE-desktop-15.1-excl-cdicon-20190219 (0.00)
[2019-12-12T17:50:44.606 CET] [debug] >>> testapi::_check_backend_response: match=generic-desktop timed out after 30 (assert_screen)
[2019-12-12T17:50:44.669 CET] [debug] no candidate needle with tag(s) 'generic-desktop' matched

Test suite description

Reproducible

Fails since (at least) Build 20191211 (current job)

Expected result

Last good: 20191210 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues

Related to openQA Tests - action #91545: [opensuse][qe-core] Upgrade tests: stall detected (consoletest_finish)Resolved

Has duplicate openQA Tests - action #64469: [sle][functional][u] test fails in consoletest_finishRejected2020-03-12

History

#1 Updated by mgriessmeier almost 2 years ago

  • Subject changed from test fails in consoletest_finish - ensure_unlocked_desktop unreliable to [functional][u][opensuse] test fails in consoletest_finish - ensure_unlocked_desktop unreliable
  • Category changed from Refactor/Code Improvements to Enhancement to existing tests

#2 Updated by okurz almost 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/3758630

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#3 Updated by okurz almost 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/3758630

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#4 Updated by SLindoMansilla over 1 year ago

Here it took too long to login, so ensure_enlocked_desktop failed: https://openqa.suse.de/tests/4236795#step/consoletest_finish/20

The dialog says "checking..." and the loop thinks that it has to unlock again.

#5 Updated by SLindoMansilla over 1 year ago

  • Assignee set to SLindoMansilla

#6 Updated by SLindoMansilla over 1 year ago

  • Has duplicate action #64469: [sle][functional][u] test fails in consoletest_finish added

#7 Updated by tjyrinki_suse about 1 year ago

  • Subject changed from [functional][u][opensuse] test fails in consoletest_finish - ensure_unlocked_desktop unreliable to [qe-core][functional][opensuse] test fails in consoletest_finish - ensure_unlocked_desktop unreliable

#8 Updated by szarate about 1 year ago

Seems that it's still there, although I'll chefkcc if for the particular case of minimalx, its a product bug, or same old story:

https://openqa.suse.de/tests/overview?arch=&machine=&modules=consoletest_finish&modules_result=failed&distri=sle&version=15-SP3&build=74.1&groupid=110#

#9 Updated by okurz about 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: minimal_x
https://openqa.suse.de/tests/5051418

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#10 Updated by okurz about 1 year ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/5130685

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#11 Updated by okurz 12 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/5188902

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#12 Updated by okurz 12 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/5188902

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#13 Updated by openqa_review 11 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/5240411

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#14 Updated by openqa_review 11 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/5303993

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#15 Updated by SLindoMansilla 11 months ago

  • Related to action #88203: [qe-core] test fails in consoletest_setup - visual artifacts from previous tty (user-console) when switching from serial terminal to tty (root-console) added

#16 Updated by SLindoMansilla 11 months ago

Sometimes this happens: #88203

#17 Updated by okurz 10 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: minimal_x
https://openqa.suse.de/tests/5421590

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#18 Updated by okurz 10 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: minimal_x
https://openqa.suse.de/tests/5421590

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#19 Updated by maritawerner 10 months ago

Just out of curiosity: this ticket is now 1 year old and nothing has moved forward. Is the issue just a minor problem that could be ignored? Could it be fixed with not so much effort? Or is it minot but complicated to fix/work around?

#20 Updated by SLindoMansilla 10 months ago

  • Due date set to 2021-03-24

maritawerner wrote:

Just out of curiosity: this ticket is now 1 year old and nothing has moved forward. Is the issue just a minor problem that could be ignored? Could it be fixed with not so much effort? Or is it minot but complicated to fix/work around?

It is a very complex problem to solve. Several proposals have been applied without long-term success.
A workaround would be to restart the failing jobs until they don't fail.

I was confident that I could find a long-term solution, but I didn't had the chance to focus on this, since there were always higher prio issues.
If you think that the workaround of restarting jobs is enough, feel free to reject this ticket. If not, let's put a due date and see if I find time until then to find a proper long-term solution.

#21 Updated by okurz 9 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/5552908

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#22 Updated by okurz 9 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/5669319

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#23 Updated by okurz 9 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/5669319

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#24 Updated by SLindoMansilla 9 months ago

  • Status changed from New to Rejected

Now is hackweek.
Feel free to reopen and unassigned me.

Workaround is to restart the affected jobs.

#25 Updated by openqa_review 8 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/5749036

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#26 Updated by tjyrinki_suse 8 months ago

  • Due date deleted (2021-03-24)
  • Status changed from Rejected to Workable
  • Assignee deleted (SLindoMansilla)
  • Priority changed from Normal to High
  • Start date deleted (2019-12-12)

This seems worthwhile to try to fix properly, it's causing a lot of time consumption retries.

#27 Updated by okurz 8 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/5846134

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#28 Updated by okurz 8 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: cryptlvm_minimal_x
https://openqa.suse.de/tests/5846134

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#29 Updated by punkioudi 8 months ago

  • Assignee set to punkioudi

#30 Updated by tjyrinki_suse 7 months ago

  • Target version set to QE-Core: Ready

#31 Updated by tjyrinki_suse 7 months ago

  • Subject changed from [qe-core][functional][opensuse] test fails in consoletest_finish - ensure_unlocked_desktop unreliable to [qe-core][functional][opensuse][needs-refining] test fails in consoletest_finish - ensure_unlocked_desktop unreliable

#32 Updated by tjyrinki_suse 7 months ago

  • Related to action #88486: [qe-core] test fails in consoletest_setup - Extract check_console_font to it's own test module, and schedule it only in the default scenario added

#33 Updated by tjyrinki_suse 7 months ago

  • Related to action #91545: [opensuse][qe-core] Upgrade tests: stall detected (consoletest_finish) added

#34 Updated by tjyrinki_suse 7 months ago

  • Related to action #87886: [qe-core] test fails in consoletest_setup - system switches to X11 console when it shouldn't added

#35 Updated by tjyrinki_suse 7 months ago

  • Related to action #34339: [qe-core][sle][functional][medium] test fails in consoletest_setup - generic text login matching too early, causing mistyping -- was " login prompt not ready to type - missing keys while typing login" added

#36 Updated by tjyrinki_suse 7 months ago

  • Subject changed from [qe-core][functional][opensuse][needs-refining] test fails in consoletest_finish - ensure_unlocked_desktop unreliable to [qe-core][functional][opensuse] test fails in consoletest_finish - ensure_unlocked_desktop unreliable

#37 Updated by tjyrinki_suse 7 months ago

  • Related to action #91112: [qe-core][qem] test fails in consoletest_setup - probably will never be fixed, remove softfail and adjust test added

#38 Updated by punkioudi 7 months ago

  • Status changed from Workable to In Progress

#39 Updated by tjyrinki_suse 7 months ago

  • Related to deleted (action #87886: [qe-core] test fails in consoletest_setup - system switches to X11 console when it shouldn't)

#40 Updated by tjyrinki_suse 7 months ago

  • Related to deleted (action #88486: [qe-core] test fails in consoletest_setup - Extract check_console_font to it's own test module, and schedule it only in the default scenario)

#41 Updated by tjyrinki_suse 7 months ago

  • Related to deleted (action #88203: [qe-core] test fails in consoletest_setup - visual artifacts from previous tty (user-console) when switching from serial terminal to tty (root-console))

#42 Updated by tjyrinki_suse 7 months ago

  • Related to deleted (action #34339: [qe-core][sle][functional][medium] test fails in consoletest_setup - generic text login matching too early, causing mistyping -- was " login prompt not ready to type - missing keys while typing login")

#43 Updated by tjyrinki_suse 7 months ago

  • Related to deleted (action #91112: [qe-core][qem] test fails in consoletest_setup - probably will never be fixed, remove softfail and adjust test)

#44 Updated by okurz 7 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: minimal_x
https://openqa.suse.de/tests/5990018

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#45 Updated by okurz 7 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: minimal_x
https://openqa.suse.de/tests/5990018

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#46 Updated by tjyrinki_suse 6 months ago

A couple of cases have been fixed by reneedling, one more to go.

Other than that, this function likely needs to be rewritten in a separate ticket.

#47 Updated by okurz 6 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: minimal_x
https://openqa.suse.de/tests/5990018

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#48 Updated by okurz 5 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: minimal_x
https://openqa.suse.de/tests/5990018

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#49 Updated by openqa_review 5 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: minimal_x
https://openqa.suse.de/tests/5990018

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed

#50 Updated by okurz 3 months ago

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days). This update was done as agreed within the SUSE QE Sync call 2021-09-01

#51 Updated by okurz about 2 months ago

  • Priority changed from High to Normal

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Normal".

#52 Updated by punkioudi 23 days ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF