⚲

Project

General

Profile

Home
Projects
Help

Search:

qe-yam

All Projects

qe-yam

Overview
Activity
Roadmap
Issues
Gantt
Calendar
Documents
Wiki

Custom queries

openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QE tools team - backlog (ready issues)
QE tools team - backlog (w/o infra)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
QE Yam backlog
QE Yam blocked issues
QE Yam closed yesterday
QE Yam issues IN_PROGRESS
QE Yam new action tickets per day
QE Yam new actions
QE Yam prio high, no updates last 4 weeks
QE Yam prio low & normal, no update for 1 year
QE Yam recjected yesterday
QE Yam resolved yesterday
QE Yam workable actions
soft failure tickets in progress
softfailure tickets resolved
softfailure tickets workable
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #128981

closed

coordination #121876: [epic] Handle openQA review failures in Yam squad - SLE 15 SP5

Run comparable test for the YaST glitch passing in O3 in OSD

Added by JERiveraMoya 12 months ago. Updated 12 months ago.

Status:

Resolved

Priority:

High

Assignee:

syrianidou_sofia

Target version:

Current

Start date:

2023-05-09

Due date:

% Done:

Estimated time:

Description

Motivation¶

Collaborate with QE tools on finding resolution for #124652

Suggestion to try out:
1 - As SLE15-SP4/SP5 fail with a ratio of 97-99% run or find according tests in Leap 15.4/5
2 - Run the corresponding Tumbleweed test on OSD to crosscheck if it also passes there

Related issues 1 (0 open — 1 closed)

Related to openQA Project - action #124652: gtk glitch not showing dialog window decoration on openQA size:M

Resolved

okurz

2023-02-15

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by JERiveraMoya 12 months ago

Related to action #124652: gtk glitch not showing dialog window decoration on openQA size:M added

Actions

Copy link

Updated by syrianidou_sofia 12 months ago

Status changed from In Progress to Resolved

I created a tumbleweed hdd on osd using this customized test: https://openqa.suse.de/tests/11076564
and then proceeded to run 100 tests for yast2_gui security module:
https://openqa.suse.de/tests/overview?distri=opensuse&build=glitch_investigation_tw&version=Tumbleweed
I have ran another 100 tests for yast2 security for SLE 15 SP5 on osd:
https://openqa.suse.de/tests/overview?distri=sle&build=glitch_investigation_SP5&version=15-SP5
The failure rate for SP5 is 5% , for Tumbleweed there is a problem with identifying a new needle created but the successful runs don't exibit the glitch at all.

Actions

Copy link

Updated by syrianidou_sofia 12 months ago

Status changed from Resolved to In Progress

will try to resolve the needle issue because the successful runs don't seem enough

Actions

Copy link

Updated by JERiveraMoya 12 months ago

what about the Leap equivalent? (point 1 in description)
How is that the failure is 5% for this case and 97% from previous investigation, could you please clarify it?

Actions

Copy link

Updated by syrianidou_sofia 12 months ago

JERiveraMoya wrote:

what about the Leap equivalent? (point 1 in description)
How is that the failure is 5% for this case and 97% from previous investigation, could you please clarify it?

The previous failure rate was collected by running the iscsi tests, now the new stats where collected by running yast2 security, because it is way simpler than customizing multimachine tests for the stats collection. If you happen to know another yast2 module that exhibited the failure more frequently, I can run tests for that as well. But seems unnecessary because I haven't seen a single failure due to the glitch on any of the opensuse distributions.

Images for Leap 15.4 created by this test: https://openqa.suse.de/tests/11096501#downloads
and Leap 15.5 by this: https://openqa.suse.de/tests/11096534#downloads

So far all tests ran on osd
5% failure for SLE15 SP5 : https://openqa.suse.de/tests/overview?distri=sle&build=glitch_investigation_SP5&version=15-SP5
0% failure for Tumbleweed : https://openqa.suse.de/tests/overview?distri=opensuse&build=glitch_investigation_tw&version=Tumbleweed
0% failure for Leap 15.4 : https://openqa.suse.de/tests/overview?distri=opensuse&build=glitch_investigation_leap_sp4&version=15.4
0% failure for Leap 15.5 : https://openqa.suse.de/tests/overview?distri=opensuse&version=Leap15.5&build=glitch_investigation_leap_sp5

Actions

Copy link