Project

General

Profile

Actions

action #98871

open

[qe-core] test fails in desktop_mainmenu as the application window for evolution from previous test module still shows up due to invalid needle

Added by okurz over 2 years ago. Updated about 1 month ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-Server-DVD-Incidents-x86_64-qam-allpatterns+addons@64bit fails in
desktop_mainmenu
as the application window for evolution from previous test module still shows up due to invalid needle.
https://openqa.suse.de/tests/7151979#step/evolution/4 shows the needle "tomcat-generic-desktop-20210908" to match which is wrong for multiple reasons:

  • There is no relation to "tomcat" here
  • There is no clean desktop shown and the needle only matches on a tiny down-arrow in the corner of the application of evolution

Test suite description

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. All modules defined in SCC_ADDONS
#20201124: added chrony-pool-openSUSE due to 15SP1 QU5 failure https://openqa.suse.de/tests/5060854

Reproducible

Fails since (at least) Build :19369:ghostscript

Expected result

Last good: :21074:ffmpeg (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by okurz over 2 years ago

I created https://gitlab.suse.de/openqa/os-autoinst-needles-sles/-/merge_requests/1563 to remove the faulty needle but that is not yet fixing the evolution test module. Retriggered https://openqa.suse.de/tests/7169148 and succeeded. Again, not fixing the problem, only limiting the impact of symptoms.

Actions #2

Updated by tjyrinki_suse about 2 years ago

  • Status changed from New to Workable
  • Start date deleted (2021-09-18)
Actions #3

Updated by slo-gin about 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions #4

Updated by slo-gin about 1 month ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF