Project

General

Profile

Actions

action #36997

closed

[opensuse][functional][u][wayland] test fails in shutdown - xterm does not start

Added by mloviska almost 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 18
Start date:
2018-06-08
Due date:
2018-09-25
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-kde-wayland@64bit_virtio fails in
shutdown

Test does not wait or verify whether xterm has been started.

Reproducible

Fails since (at least) Build 20180522

Expected result

Last good: 20180521 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (0 open1 closed)

Blocked by openQA Tests - coordination #35215: [functional][u][epic][medium] test fails on shutdown moduleResolvedoorlov2018-04-192018-09-25

Actions
Actions #1

Updated by okurz almost 6 years ago

  • Subject changed from [opensuse][functional][u] test fails in shutdown - xterm does not start to [opensuse][functional][u][wayland] test fails in shutdown - xterm does not start
  • Due date set to 2018-07-17
  • Target version set to Milestone 17

I think github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4908 did not fix this completely

Code behaves like this now:

[2018-06-08T08:01:26.0642 UTC] [debug] /var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/tests/x11/shutdown.pm:24 called testapi::x11_start_program
[2018-06-08T08:01:26.0642 UTC] [debug] <<< testapi::assert_screen(mustmatch=[
  'xterm',
  'desktop-runner-plasma-suggestions'
], no_wait=0, timeout=90)
[2018-06-08T08:01:26.0672 UTC] [debug] MATCH(xterm-started-20150325:0.00)
[2018-06-08T08:01:26.0700 UTC] [debug] MATCH(xterm-started-20150430:0.00)
[2018-06-08T08:01:26.0726 UTC] [debug] MATCH(xterm-started-20170125:0.00)
[2018-06-08T08:01:26.0756 UTC] [debug] MATCH(xterm-started-kde-20171111:0.00)
[2018-06-08T08:01:26.0781 UTC] [debug] MATCH(desktop-runner-plasma-suggestions-20180423:1.00)
[2018-06-08T08:01:26.0924 UTC] [debug] >>> testapi::_handle_found_needle: found desktop-runner-plasma-suggestions-20180423, similarity 1.00 @ 243/1
[2018-06-08T08:01:26.0924 UTC] [debug] /var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/tests/x11/shutdown.pm:25 called testapi::script_sudo
[2018-06-08T08:01:26.0925 UTC] [debug] <<< testapi::script_sudo(name='echo \'ForwardToConsole=yes\' >> /etc/systemd/journald.conf', wait=2)

so somehow the test is accepting "desktop-runner-plasma-suggestions" and not actually waiting for an xterm window but it should.

The relevant test code is in lib/susedistribution.pm:

    my @target = ref $args{target_match} eq 'ARRAY' ? @{$args{target_match}} : $args{target_match};
    for (1 .. 3) {
        push @target, check_var('DESKTOP', 'kde') ? 'desktop-runner-plasma-suggestions' : 'desktop-runner-border';
        assert_screen([@target], $args{match_timeout}, no_wait => $args{match_no_wait});
        last unless (match_has_tag 'desktop-runner-border' || match_has_tag 'desktop-runner-plasma-suggestions');
        wait_screen_change {
            send_key 'ret';
        };
    }
    # asserting program came up properly
    die "Did not find target needle for tag(s) '@target'" if (match_has_tag 'desktop-runner-border' || match_has_tag 'desktop-runner-plasma-suggestions');

I assumed this would make sure that "xterm" has to be displayed as the last screen or the die would be called but that does not seem to be the case.

Logic needs to be re-evaluated.

Actions #2

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 17 to Milestone 17
Actions #3

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 17 to Milestone 18
Actions #4

Updated by okurz almost 6 years ago

  • Due date changed from 2018-07-17 to 2018-07-31

It's hackweek time!

Actions #5

Updated by okurz almost 6 years ago

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

already on it to look into the behaviour of desktop runner

Actions #6

Updated by okurz almost 6 years ago

  • Blocked by coordination #35215: [functional][u][epic][medium] test fails on shutdown module added
Actions #7

Updated by okurz almost 6 years ago

  • Status changed from In Progress to Blocked
  • Assignee changed from okurz to oorlov

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5409 is applied but still the test scenario is very unstable. The latest job https://openqa.opensuse.org/tests/710661#step/reboot_plasma5/10 e.g. shows the frowning smiley in systray showing a crashed application. The screen should match as soft_fail, not green after a bug has been reported, more data to this should be recorded, e.g. post_fail_hook. But first I recommend in https://openqa.opensuse.org/tests/710661#step/shutdown/10 to execute a post_fail_hook to gather data from the still active system.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5314 from @oorlov should be the first step

Actions #8

Updated by mgriessmeier over 5 years ago

  • Due date changed from 2018-07-31 to 2018-08-14
Actions #9

Updated by okurz over 5 years ago

  • Due date changed from 2018-08-14 to 2018-08-28

bulk move to next sprint as could not be discussed in SR

Actions #11

Updated by oorlov over 5 years ago

  • Status changed from Blocked to In Progress

I've investigated the issue with shutdown and it didn't fail for the last 15 days. Also after adding 'cleanup_before_shutdown' module, there is no xterm call in 'shutdown.pm' anymore. So the behavior from the description is not reproducible. It fails on 'assert_shutdown' instead now.

I've added DEBUG_SHUTDOWN parameter. Will wait for the statistics and more detailed logs.

Actions #12

Updated by nicksinger over 5 years ago

  • Status changed from In Progress to Feedback
Actions #13

Updated by mgriessmeier over 5 years ago

  • Due date changed from 2018-08-28 to 2018-09-11
Actions #14

Updated by mgriessmeier over 5 years ago

  • Due date changed from 2018-09-11 to 2018-09-25

let's discuss the state offline

Actions #15

Updated by oorlov over 5 years ago

Not able to gather statistics for shutdown module, as jobs failed in the modules before it.

The latest one is passed. So, hopefully next builds will help to gather more statistics.

Actions #16

Updated by oorlov over 5 years ago

  • Status changed from Feedback to Resolved

So, I'm closing the ticket as the issue is not reproduced anymore. Also, the scope is changed - there is no xterm call in 'shutdown' module anymore.

Actions

Also available in: Atom PDF