Project

General

Profile

Actions
Copy link

action #48899

closed

[opensuse] kdelive/upgrade: does not handle package notifications

Added by dimstar about 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Category:
Bugs in existing tests
Target version:
-
Start date:
2019-03-08
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-KDE-Live-x86_64-kde_live_upgrade_leap_42.3@64bit-2G fails in
await_install

Test suite description

Uses the live installer on the kde live media for upgrading the system.

Reproducible

Fails since (at least) Build 20190307 (current job)

Expected result

Last good: 20190301 (or more recent)

Further details

Always latest result in this scenario: latest

Related issues 1 (0 open — 1 closed)

Related to openQA Tests - action #63346: [tools][sporadic] false-positive match on "screenlock-xscreensaver-20180821" when instead a console prompt is shownResolvedokurz2020-02-10

Actions
Actions
Copy link
 #1

Updated by SLindoMansilla about 5 years ago

  • Subject changed from kidelive/upgrade: does not handle package notifications to [opensuse] kidelive/upgrade: does not handle package notifications

As a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).

Please, feel free to adjust the category or the "[label]" if you think different.

Actions
Copy link
 #2

Updated by dimstar about 5 years ago

  • Subject changed from [opensuse] kidelive/upgrade: does not handle package notifications to [opensuse] kdelive/upgrade: does not handle package notifications
Actions
Copy link
 #3

Updated by okurz about 4 years ago

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

Currently the scenario https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=KDE-Live&machine=64bit-2G&test=kde_live_upgrade_leap_42.3&version=Tumbleweed times out after 4h being stuck in await_install. I wonder if it eventually can finish when I increase the MAX_JOB_TIME further:

openqa-clone-job --skip-chained-deps --within-instance https://openqa.opensuse.org 1165210 MAX_JOB_TIME=$((12*60*60))

Created job #1165262: opensuse-Tumbleweed-KDE-Live-x86_64-Build20200204-kde_live_upgrade_leap_42.3@64bit-2G -> https://openqa.opensuse.org/t1165262

Was obsoleted by new build, trying again:

openqa-clone-job --skip-chained-deps --within-instance https://openqa.opensuse.org 1165610 MAX_JOB_TIME=$((12*60*60))

Created job #1165619: opensuse-Tumbleweed-KDE-Live-x86_64-Build20200205-kde_live_upgrade_leap_42.3@64bit-2G -> https://openqa.opensuse.org/t1165619

EDIT: I think this will not work. The code in "await_install" is only decreasing the timeout if check_screen does not match but it repeatedly matches on "screenlock" even though it's a black tty screen. Probably the screenlock with all black can only happen in gnome context. I don't think plasma has the same.
I propose to match only on minimalx https://github.com/os-autoinst/os-autoinst-needles-opensuse/pull/633

Actions
Copy link
 #4

Updated by okurz about 4 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #5

Updated by okurz about 4 years ago

needle change merged. That helped to prevent an incomplete as now we have a failed tests which also correctly executes the post_fail_hook. Either the installer crashes or we are really in a weird screenlock but the system doesn't unlock on key press.

I suggest the following:

  1. Change await_install to prevent an endless loop on wrong screen match with no reaction
  2. investigate the log files for what went wrong

For 1.:

 for i in https://openqa.opensuse.org/tests/1166278 https://openqa.opensuse.org/tests/1162613 https://openqa.opensuse.org/tests/1165657; do openqa-clone-custom-git-refspec github.com/okurz/os-autoinst-distri-opensuse/tree/enhance/await_install $i ; done

openqa-clone-custom-git-refspec doesn't support branches with "/" included, workaround:

for i in https://openqa.opensuse.org/tests/1166278 https://openqa.opensuse.org/tests/1162613 https://openqa.opensuse.org/tests/1165657; do openqa-clone-custom-git-refspec https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9533 $i ; done

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

Actions
Copy link
 #6

Updated by ggardet_arm about 4 years ago

It does break gnome 'shutdown' test on create_hdd_gnome-x11 for aarch64 Tumbleweed:
https://openqa.opensuse.org/tests/1169347#next_previous

Also consoletest_finish in upgrade_Leap_15.x_gnome:
https://openqa.opensuse.org/tests/1168699#next_previous
And in consoletest_finish in gnome-ext4 (Leap 15.2 aarch64):
https://openqa.opensuse.org/tests/1167582#step/consoletest_finish/12

Probably more.

If needed, this needle has the blackscreen tag, if you want to check.

Revert PR: https://github.com/os-autoinst/os-autoinst-needles-opensuse/pull/635

Actions
Copy link
 #7

Updated by okurz about 4 years ago

  • Status changed from Feedback to Workable

thanks for handling the failures (by reverting). With this I know which scenarios to check and can try again.

EDIT: I merged the test changes in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9533 to prevent an endless-loop (but not fix the failure).

EDIT: guillaume_g: the needle I changed and you reverted is actually causing IMHO quite severe mismatches, e.g. see https://openqa.opensuse.org/tests/1169511#step/updates_packagekit_gpk/1 where it matches but there is a prompt sign in top left corner. I will try to create a new, stricter needle that should not cause false-positives

Actions
Copy link
 #8

Updated by okurz about 4 years ago

  • Related to action #63346: [tools][sporadic] false-positive match on "screenlock-xscreensaver-20180821" when instead a console prompt is shown added
Actions
Copy link
 #9

Updated by okurz about 4 years ago

  • Status changed from Workable to In Progress

@ggardet_arm the bad needle "screenlock-xscreensaver-20180821" causes even more problems. E.g. in https://bugzilla.opensuse.org/show_bug.cgi?id=1164311 zluo reported something about an error message which has nothing to do with the test failure which is very related to the bad needle causing false-positive matches. I will delete the needle now again and try to make sure that no test fails for missing it but instead ensure to have a proper, strict needle instead where needed.

Deleted needle with
https://github.com/os-autoinst/os-autoinst-needles-opensuse/pull/646 and will now handle the tests.

Finally https://openqa.opensuse.org/tests/1182649# has a useful result again. It fails but with proper execution of the post_fail_hook after 1h and not as incomplete timing out after 4h. Now I think https://openqa.opensuse.org/tests/1182649#step/await_install/297 has useful logs from yast installer crashes but one should crosscheck other logs as well, e.g. check if the list of processes also shows that something is wrong, e.g. installer process crashed or so.

Actions
Copy link
 #10

Updated by okurz about 4 years ago

  • Subject changed from [opensuse] kdelive/upgrade: does not handle package notifications to [opensuse][functional][u] kdelive/upgrade: does not handle package notifications
  • Status changed from In Progress to Workable
  • Assignee deleted (okurz)

So much for my part. Now with the test failures more obvious I leave some work for others :)

Actions
Copy link
 #11

Updated by okurz about 4 years ago

  • Subject changed from [opensuse][functional][u] kdelive/upgrade: does not handle package notifications to [opensuse] kdelive/upgrade: does not handle package notifications
  • Status changed from Workable to Resolved
  • Assignee set to okurz

Actually it seems that package notification popups are not the problem and also my changes made the post_fail_hook work so I did report https://bugzilla.opensuse.org/show_bug.cgi?id=1165912 about the installer or plasma session probably crashing

Actions
Copy link

Also available in: Atom PDF