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.
0%
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
Updated by SLindoMansilla about 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
Updated by zluo about 4 years ago
- Status changed from Workable to In Progress
- Assignee set to zluo
checking
Updated by zluo about 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.
Updated by zluo about 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
Updated by zluo about 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.
Updated by zluo about 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.
Updated by zluo about 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.
Updated by zluo about 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.
Updated by SLindoMansilla about 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)
Updated by zluo about 4 years ago
to check later:
Updated by zluo about 4 years ago
- Status changed from In Progress to Resolved
checked the results and it is resolved, thanks @SLindoMansilla
Updated by SLindoMansilla about 4 years ago
- Status changed from Resolved to Workable
- Assignee changed from zluo to SLindoMansilla
Still happening: https://openqa.suse.de/tests/4110988#step/vnc_two_passwords/23
Updated by SLindoMansilla about 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
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
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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
https://openqa.suse.de/tests/4341427
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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
https://openqa.suse.de/tests/4341427
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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
https://openqa.suse.de/tests/4341427
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by SLindoMansilla almost 4 years ago
- Status changed from In Progress to Workable
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
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/5307279
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by SLindoMansilla about 3 years ago
- Status changed from Workable to New
- Assignee deleted (
SLindoMansilla)
No time to work on this :(
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/5752648
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
Updated by szarate about 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
Updated by tjyrinki_suse about 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.
Updated by tjyrinki_suse about 3 years ago
- Target version changed from Milestone 30 to QE-Core: Ready
Updated by tjyrinki_suse about 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)
Updated by tjyrinki_suse almost 3 years ago
- Status changed from Workable to In Progress
- Assignee set to dvenkatachala
Updated by tjyrinki_suse almost 3 years ago
- Target version deleted (
QE-Core: Ready)
Delaying until next sprint.
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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
Updated by openqa_review 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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released"
- The label in the openQA scenario is removed
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:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The label in the openQA scenario is removed
Updated by tjyrinki_suse about 2 years ago
- Related to action #107341: [qe-core] test fails in vnc_two_passwords added
Updated by szarate about 2 years ago
- Status changed from New to Rejected
- Assignee set to szarate