Project

General

Profile

action #64568

[qe-core][functional][needs-refining] test fails in vnc_two_passwords - Test fails due to (apparent) timeout

Added by szarate over 2 years ago. Updated 4 months ago.

Status:
Rejected
Priority:
Low
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

It seems that wait_serial didn't find any match on time and the test failed maybe bumping the timeout by 10 more seconds?

openQA test in scenario sle-15-SP2-Online-ppc64le-extra_tests_gnome_sdk@ppc64le fails in
vnc_two_passwords

Suggestions

  • This needs investigation. Probably a race condition (sub generate_vnc_events?)

Reproducible

Fails since (at least) Build 150.1

Expected result

Last good: 146.1 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues

Related to openQA Tests - action #107341: [qe-core] test fails in vnc_two_passwordsRejected

History

#1 Updated by SLindoMansilla about 2 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Target version set to Milestone 30
  • Estimated time set to 42.00 h

#2 Updated by zluo about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to zluo

checking

#3 Updated by zluo about 2 years ago

https://openqa.suse.de/tests/4077630#step/vnc_two_passwords/18 shows that it looks different after

# Close xev 
send_key 'ctrl-c';

It still fails at command 'wc -l /tmp/xev_log | grep "0 "'

This is a sporadic issue atm, 1 failure of 51 test runs.

#4 Updated by zluo about 2 years ago

Add wait_still_screen after ctrl-c, to give a little more time for next command at prompt, because I think if typing command can might hit issue when xev is not close yet.

# Close xev
send_key 'ctrl-c';
wait_still_screen;
# Check if xev recorded events or not - RO/RW mode
if ($opt->{change}) {
assert_script_run '[ -s /tmp/xev_log ]';
}

else {
my $timeout = 30;
$timeout = 60 if is_ppc64le;
assert_script_run 'wc -l /tmp/xev_log | grep "^0 "', $timeout;
}
save_screenshot;
assert_script_run 'rm /tmp/xev_log';
}

test:

https://openqa.suse.de/tests/4079375#step/vnc_two_passwords/16

#5 Updated by zluo about 2 years ago

https://openqa.suse.de/tests/4079389#step/vnc_two_passwords/16 shows performance issue, so this could be also an issue in general.

#6 Updated by zluo about 2 years ago

"QEMU" : "ppc64",
"QEMUCPU" : "host",
"QEMUCPUS" : "1",
"QEMUMACHINE" : "usb=off",
"QEMUPORT" : 20022,
"QEMURAM" : "1536",
"QEMUTHREADS" : "1",
"QEMUVGA" : "std",
"QEMU_COMPRESS_QCOW2" : 1,

the above settings are used for production. more tests failed clearly if I compare tests with timeout 60 sec.

#7 Updated by zluo about 2 years ago

https://openqa.suse.de/tests/4091217#step/vnc_two_passwords/25 shows that xev log is not yet empty:

as assert_script_run 'wc -l /tmp/xev_log | grep "0 "'; is called.

This might be related to the issue that xev is hanging or not closed in time.

#8 Updated by zluo about 2 years ago

Repeat send_key ctrl-c and wait for closing xev in vnc_two_passwords.pm

this helps now.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9946 updated.

#9 Updated by SLindoMansilla about 2 years ago

PR to improve synchronization point: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10004
If ppc64le still fails, it could be:

Scenario A

ppc64le needs more time to close xev. for that, the timeout of the wait_serial can be increased. (please avoid any kind of "sleep-like" instruction unless other options are tried)

Scenario B

Even after process started directly by xev command is stopped, it could be that a thread/sub-process is still hung, in that case, ps -C cmd should be used to look for the guilty process and only continue after that process has exited. (please avoid any kind of "sleep-like" instruction unless other options are tried)

#11 Updated by zluo about 2 years ago

  • Status changed from In Progress to Resolved

checked the results and it is resolved, thanks @SLindoMansilla

#12 Updated by SLindoMansilla about 2 years ago

  • Status changed from Resolved to Workable
  • Assignee changed from zluo to SLindoMansilla

#13 Updated by SLindoMansilla about 2 years ago

I am not able to reproduce the new fail locally, we need more logs to investigate the source of the problem: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10040

#14 Updated by SLindoMansilla about 2 years ago

  • Status changed from Workable to In Progress

Die if vncviewer or xev didn't finished after stopping them: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10218

#15 Updated by okurz about 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: extra_tests_gnome@ppc64le-2g
https://openqa.suse.de/tests/4261368

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

#16 Updated by okurz about 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: extra_tests_gnome@ppc64le-2g
https://openqa.suse.de/tests/4311963

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

#17 Updated by okurz about 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: extra_tests_gnome
https://openqa.suse.de/tests/4341427

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 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: extra_tests_gnome
https://openqa.suse.de/tests/4341427

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 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: extra_tests_gnome
https://openqa.suse.de/tests/4341427

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

#20 Updated by SLindoMansilla almost 2 years ago

  • Status changed from In Progress to Workable

#21 Updated by tjyrinki_suse over 1 year ago

  • Subject changed from [functional][u] test fails in vnc_two_passwords - Test fails due to (apparent) timeout to [qe-core][functional] test fails in vnc_two_passwords - Test fails due to (apparent) timeout

#22 Updated by okurz over 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: extra_tests_gnome
https://openqa.suse.de/tests/5307279

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 over 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: extra_tests_gnome@ppc64le-2g
https://openqa.suse.de/tests/5553225

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 okurz over 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: extra_tests_gnome@ppc64le-2g
https://openqa.suse.de/tests/5553225

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

#25 Updated by SLindoMansilla over 1 year ago

  • Status changed from Workable to New
  • Assignee deleted (SLindoMansilla)

No time to work on this :(

#26 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: extra_tests_gnome
https://openqa.suse.de/tests/5752648

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

#27 Updated by szarate about 1 year ago

I think moving the mouse back to the xev window, clicking and then sending the alt+c could work, or simply: send_key_until_needlematch("xev-finished", 'alt-c', 5, 5) or something similar. Another idea is to kill xev from serial terminal

#28 Updated by tjyrinki_suse about 1 year ago

  • Status changed from New to Workable
  • Priority changed from Normal to High
  • Start date deleted (2020-03-18)

Sounds like good ideas to try.

This problem still happens on recent Functional runs.

#29 Updated by tjyrinki_suse about 1 year ago

  • Target version changed from Milestone 30 to QE-Core: Ready

#30 Updated by tjyrinki_suse about 1 year ago

  • Subject changed from [qe-core][functional] test fails in vnc_two_passwords - Test fails due to (apparent) timeout to [qe-core][functional][needs-refining] test fails in vnc_two_passwords - Test fails due to (apparent) timeout
  • Description updated (diff)

#31 Updated by tjyrinki_suse about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to dvenkatachala

#32 Updated by tjyrinki_suse about 1 year ago

  • Target version deleted (QE-Core: Ready)

Delaying until next sprint.

#33 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: extra_tests_gnome
https://openqa.suse.de/tests/5991384

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

#34 Updated by szarate about 1 year ago

  • Status changed from In Progress to New
  • Assignee deleted (dvenkatachala)
  • Priority changed from High to Low

We could unschedule the module or straight up rewrite it in a less complicated fashion, also... vnc is being tested in the desktop jog group

https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Online&machine=64bit-virtio-vga&test=desktopapps-remote-client1&version=15-SP3

#35 Updated by openqa_review 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: extra_tests_gnome
https://openqa.suse.de/tests/5991384

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

#36 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: extra_tests_gnome
https://openqa.suse.de/tests/5991384

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

#37 Updated by tjyrinki_suse 4 months ago

  • Related to action #107341: [qe-core] test fails in vnc_two_passwords added

#38 Updated by szarate 4 months ago

  • Status changed from New to Rejected
  • Assignee set to szarate

Also available in: Atom PDF