Project

General

Profile

Actions
Copy link

action #119416

closed

[qe-core][functional]test fails in vnc_two_passwords on aarch64 at couple of places because of sporadic performance issue

Added by rfan1 about 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
zluo
Category:
Bugs in existing tests
Target version:
QA - QE-Core: Ready
Start date:
2022-10-26
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:
bugbusters

Description

Observation

openQA test in scenario sle-15-SP5-Online-aarch64-extra_tests_gnome@aarch64 fails in
vnc_two_passwords

Test suite description

Maintainer: QE Core, asmorodskyi. Extra tests which were designed to run on gnome , VNC_STALL_THRESHOLD is needed for xen svirt to don't turn off the scrreen after default 4 sec

New version of extra_tests_on_gnome for yaml scheduling

Reproducible

Fails since (at least) Build 25.1

Expected result

Last good: 24.1 (or more recent)

Further details

Always latest result in this scenario: latest

Related issues 1 (0 open — 1 closed)

Related to openQA Tests - action #120282: [qe-core][functional][aarch64] test fails in vnc_two_passwords because xev hangsResolvedzluo2022-11-10

Actions
Actions
Copy link
 #1

Updated by zluo about 2 years ago

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

take over and check

Actions
Copy link
 #2

Updated by zluo about 2 years ago

https://openqa.suse.de/tests/9855282#next_previous
shows that some tests runs failed of 100.

Actions
Copy link
 #3

Updated by zluo about 2 years ago

openqaworker-arm-3:16, openqaworker-arm-3:17, openqaworker-arm-3:8, openqaworker-arm-2:5, openqaworker-arm-2:18, openqaworker-arm-2:11, openqaworker-arm-3:2, openqaworker-arm-3:5, openqaworker-arm-3:19, openqaworker-arm-2:15, openqaworker-arm-2:8, openqaworker-arm-2:7

I checked and found out that above workers have performance issue with the test.

Actions
Copy link
 #5

Updated by okurz about 2 years ago

There is no difference between the instances within one host. They are all native qemu on the hosts

Actions
Copy link
 #6

Updated by zluo about 2 years ago

https://openqa.suse.de/tests/9870904#step/vnc_two_passwords/23

openqaworker-arm-2:12 failed even earlier.

Actions
Copy link
 #7

Updated by zluo about 2 years ago

https://openqa.suse.de/tests/9873285#next_previous looks pretty good now, but failed at another stage:

Test died: xev not finished at /var/lib/openqa/pool/3/os-autoinst-distri-opensuse/tests/x11/vnc_two_passwords.pm line 144
issue with 'send_key' to close xev doesn't work always.

https://openqa.suse.de/tests/9873001#step/vnc_two_passwords/37 looks like

enter_cmd "(trap 'echo xev-finished >/dev/$serialdev' SIGINT; xev -display $display -root | tee /tmp/xev_log) "; triggered, but generate_vnc_events $opt->{pw}; doesn't work or could not finish. That is why 'send_key' to close xev failed.

Actions
Copy link
 #8

Updated by zluo about 2 years ago

https://openqa.suse.de/tests/9899633#step/vnc_two_passwords/57
typing issue, but this has not to do with original issue.

Actions
Copy link
 #9

Updated by zluo about 2 years ago

at moment I have sporadic issue with xev:

https://openqa.suse.de/tests/9901237#step/vnc_two_passwords/37

tried even two times to finish xev, but without success.

Actions
Copy link
 #10

Updated by zluo about 2 years ago

  • Related to action #120282: [qe-core][functional][aarch64] test fails in vnc_two_passwords because xev hangs added
Actions
Copy link
 #11

Updated by zluo about 2 years ago

https://openqa.suse.de/tests/9922866#step/vnc_two_passwords/12 failed at zypper_call already, but this is not related to original issue.

rpm -q tigervnc failed because performance issue:

https://openqa.suse.de/tests/9922880#step/vnc_two_passwords/55

leads to failed echo command.

But it looks much better, the last 100 test runs looks good except one issue with xev:
https://openqa.suse.de/tests/9922873#step/vnc_two_passwords/35

will add poo#120282 in record_info.

Actions
Copy link
 #12

Updated by zluo about 2 years ago

  • Subject changed from [qe-core][functional]test fails in vnc_two_passwords on aarch64 platform, seems to be a timing issue to [qe-core][functional]test fails in vnc_two_passwords on aarch64 at couple of places because of sporadic performance issue
Actions
Copy link
 #14

Updated by zluo about 2 years ago

https://openqa.suse.de/tests/9931055#step/vnc_two_passwords/11
could not resovle openqa.suse.de
network issue.

Actions
Copy link
 #15

Updated by zluo about 2 years ago

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15830 updated and checked against opensuse aarch64 as well.

Actions
Copy link
 #16

Updated by zluo about 2 years ago

  • Status changed from In Progress to Resolved

PR merged

Actions
Copy link
 #17

Updated by openqa_review almost 2 years ago

  • Status changed from Resolved to Feedback

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/10028274#step/vnc_two_passwords/1

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 bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #18

Updated by zluo almost 2 years ago

  • Status changed from Feedback to Resolved

no issue for recent test runs on OSD, set it as resolved, PR works so far okay and stable.

Actions
Copy link
 #19

Updated by openqa_review almost 2 years ago

  • Status changed from Resolved to Feedback

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/10434861#step/vnc_two_passwords/1

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 bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 48 days if nothing changes in this ticket.

Actions
Copy link
 #20

Updated by zluo almost 2 years ago

  • Status changed from Feedback to In Progress

since this issue is persistent and it looks not better than before, I will check and think about a better way for this sporadic performance issue on aarch64.

Actions
Copy link
 #21

Updated by zluo over 1 year ago

  • Status changed from In Progress to Feedback

another try to work around this sporadic performance issue:

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

Actions
Copy link
 #22

Updated by mgrifalconi over 1 year ago

  • Status changed from Feedback to Resolved

Hello, let's try to resolve it one more time to cleanup the queue. The automation will open it again in case of further issue.

Actions
Copy link

Also available in: Atom PDF