QA (public) » openQA Project (public) » openQA Tests (public)

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 "⁰ "'

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

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

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

"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.

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 "⁰ "'; is called.

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

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.

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)

to check later:

https://openqa.opensuse.org/t1228812

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

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

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

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

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

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

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

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

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

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

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

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

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

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