Project

General

Profile

Actions

action #64568

closed

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

Added by szarate about 4 years ago. Updated about 2 years 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 1 (0 open1 closed)

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

Actions
Actions #1

Updated by SLindoMansilla almost 4 years ago

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

Updated by zluo almost 4 years ago

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

checking

Actions #3

Updated by zluo almost 4 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.

Actions #4

Updated by zluo almost 4 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

Actions #5

Updated by zluo almost 4 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.

Actions #6

Updated by zluo almost 4 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.

Actions #7

Updated by zluo almost 4 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.

Actions #8

Updated by zluo almost 4 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.

Actions #9

Updated by SLindoMansilla almost 4 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)

Actions #10

Updated by zluo almost 4 years ago

Actions #11

Updated by zluo almost 4 years ago

  • Status changed from In Progress to Resolved

checked the results and it is resolved, thanks @SLindoMansilla

Actions #12

Updated by SLindoMansilla almost 4 years ago

  • Status changed from Resolved to Workable
  • Assignee changed from zluo to SLindoMansilla
Actions #13

Updated by SLindoMansilla almost 4 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

Actions #14

Updated by SLindoMansilla almost 4 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

Actions #15

Updated by okurz almost 4 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
Actions #16

Updated by okurz almost 4 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
Actions #17

Updated by okurz over 3 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
Actions #18

Updated by okurz over 3 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
Actions #19

Updated by okurz over 3 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
Actions #20

Updated by SLindoMansilla over 3 years ago

  • Status changed from In Progress to Workable
Actions #21

Updated by tjyrinki_suse over 3 years 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
Actions #22

Updated by okurz about 3 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/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
Actions #23

Updated by okurz about 3 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/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
Actions #24

Updated by okurz about 3 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/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
Actions #25

Updated by SLindoMansilla about 3 years ago

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

No time to work on this :(

Actions #26

Updated by okurz almost 3 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/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
Actions #27

Updated by szarate almost 3 years 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

Actions #28

Updated by tjyrinki_suse almost 3 years 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.

Actions #29

Updated by tjyrinki_suse almost 3 years ago

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

Updated by tjyrinki_suse almost 3 years 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)
Actions #31

Updated by tjyrinki_suse almost 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to dvenkatachala
Actions #32

Updated by tjyrinki_suse almost 3 years ago

  • Target version deleted (QE-Core: Ready)

Delaying until next sprint.

Actions #33

Updated by okurz almost 3 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/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
Actions #34

Updated by szarate almost 3 years 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

Actions #35

Updated by openqa_review over 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/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
Actions #36

Updated by okurz over 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/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
Actions #37

Updated by tjyrinki_suse about 2 years ago

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

Updated by szarate about 2 years ago

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

Also available in: Atom PDF