Project

General

Profile

Actions

action #152548

closed

coordination #151816: [epic] Handle openQA fixes and job group setup

Mismatch for needle with tag `yast2_snapper-unselected_testdata` in module `x11/yast2_snapper.pm`

Added by lmanfredi 10 months ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Target version:
-
Start date:
2023-12-13
Due date:
% Done:

0%

Estimated time:

Description

Motivation

In YaST job group for test suite yast2_gui for ARCH ppc64le and x86_64 there is a mismatch for needle with tag yast2_snapper-unselected_testdata in module x11/yast2_snapper.pm:

tests/x11/yast2_snapper.pm:62 called y2snapper_common::y2snapper_show_changes_and_delete -> lib/y2snapper_common.pm:170 called assert_screen 'yast2_snapper-unselected_testdata';

Scope

Acceptance criteria

  • AC1: create the needle that match the current image with tag yast2_snapper-unselected_testdata
Actions #1

Updated by JERiveraMoya 10 months ago

Not sure if the needle, it could be also a problem with the known refresh bug.

Actions #2

Updated by JERiveraMoya 10 months ago

  • Tags set to qe-yam-dec-sprint
  • Status changed from New to Workable
  • Parent task set to #151816
Actions #3

Updated by syrianidou_sofia 10 months ago

  • Status changed from Workable to In Progress
  • Assignee set to syrianidou_sofia
Actions #4

Updated by syrianidou_sofia 10 months ago ยท Edited

Added the workaround and running some VRs: https://openqa.suse.de/tests/13103164#next_previous

Workaround PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18329

The glitch workaround was applied two times in yast2_snapper and there was a modification in yast2_bootloader as th eworkaround was applied after attempting to switch to kernel parameters but then it made the tab to return to the main one for bootloader parameters.

Actions #5

Updated by openqa_review 10 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: yast2_gui@ppc64le-2g
https://openqa.suse.de/tests/13005476#step/yast2_snapper/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 #6

Updated by JERiveraMoya 9 months ago

  • Tags changed from qe-yam-dec-sprint, qe-yam-jan-sprint to qe-yam-jan-sprint
Actions #7

Updated by JERiveraMoya 9 months ago

  • Tags changed from qe-yam-jan-sprint to qe-yam-dec-sprint
  • Status changed from In Progress to Resolved

Let's resolve it and reopen if we see the glitch again.

Actions

Also available in: Atom PDF