action #33517: [functional][y][yast][sporadic][medium] yast2_control_center: possible conflict with PackageKit doing background refresh - openQA Tests (public) - openSUSE Project Management Tool

Custom queries

All open Feature tests
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
QAM
QE tools team - backlog (dev)
QE tools team - backlog (ready issues)
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 (dev)
QE tools team - non-estimated (unblocked) issues (infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - SLO high forecast
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
SLE15 Migration Open Tickets
SLE15 SP1 Migration Open Tickets
SLE15SP3 Migration open ticket
SLE15SP3 Security open ticket
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #33517

closed

[functional][y][yast][sporadic][medium] yast2_control_center: possible conflict with PackageKit doing background refresh

Added by dimstar almost 7 years ago. Updated over 6 years ago.

Status:

Resolved

Priority:

Urgent

Assignee:

cwh

Category:

Bugs in existing tests

Target version:

openQA Project (public) - Milestone 16

Start date:

2018-03-20

Due date:

2018-05-08

% Done:

Estimated time:

Difficulty:

medium

Description

Observation¶

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_gui@64bit fails in
yast2_control_center

Reproducible¶

Fails since (at least) Build 20180314

Expected result¶

Last good: 20180313 (or more recent)

Suggestions¶

Call pkcon_quit within test module.

As an alternative, we can explore if pressing yes is stable enough to fix in the test. (First option is still preferable)

Further details¶

Always latest result in this scenario: latest

either we explicitly terminate PK before hand or we ensure the pk refresh is completed (the test sometimes passes, most of the times fails).

History
Notes
Property changes

Actions

Copy link

Updated by okurz almost 7 years ago

Subject changed from yast2_control_center: possible conflict with PackageKit doing background refresh to [functional][y][yast]yast2_control_center: possible conflict with PackageKit doing background refresh
Target version set to Milestone 16

Actions

Copy link

Updated by okurz almost 7 years ago

Due date set to 2018-04-10
Priority changed from Normal to Urgent
Target version changed from Milestone 16 to Milestone 15

failing reproducibly every time since the mentioned build

Actions

Copy link

Updated by dimstar almost 7 years ago

failing reproducibly every time since the mentioned build

not really - whenever the PK conflict does not show up (and I see it) I can create one or two more needles. The failure always happens to be in the same module, but it is not always the exact same error

e.g. https://openqa.opensuse.org/tests/643136#step/yast2_control_center/20 failed on missing needles for the printer config

Actions

Copy link

Updated by riafarov almost 7 years ago

Subject changed from [functional][y][yast]yast2_control_center: possible conflict with PackageKit doing background refresh to [functional][y][yast][sporadic] yast2_control_center: possible conflict with PackageKit doing background refresh
Description updated (diff)
Status changed from New to Workable

I see, in cases like these feel free to add the subject keyword "[sporadic]" so that no one states: "One job did not fail, is it solved?" ;)

Actions

Copy link

Updated by cwh almost 7 years ago

Assignee set to cwh

So unconditionally calling pkcon quit before starting sw_single should maybe solve that problem, shouldn't it?

Actions

Copy link

Updated by okurz almost 7 years ago

Subject changed from [functional][y][yast][sporadic] yast2_control_center: possible conflict with PackageKit doing background refresh to [functional][y][yast][sporadic][medium] yast2_control_center: possible conflict with PackageKit doing background refresh

yes

Actions

Copy link

Updated by cwh almost 7 years ago

Status changed from Workable to In Progress

Actions

Copy link

Updated by cwh almost 7 years ago

Difficulty set to medium

Actions

Copy link

Updated by cwh almost 7 years ago

My first try to solve this by a simple "pkcon quit" was not successful:
http://boltzmann.suse.de/tests/43#step/yast2_control_center/2

Using this way we don't know how long PackageKit will take until it actually quits. So maybe it is better to go for the button-clicking solution.

Actions

Copy link

#10

Updated by okurz almost 7 years ago

yes, I also do not have any better plan now. Should be ok to have a multi-tag assert_screen with if match_has_tag. https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/x11/kontact.pm can provide an example.

Actions

Copy link

#11

Updated by cwh almost 7 years ago

Status changed from In Progress to Feedback

The clicking approach works – using a wisely selected needle even with all the repeated dialogs that ask to try to quit again.
http://boltzmann.suse.de/tests/55

Here the PR for the code:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4775

and the needle:
https://github.com/os-autoinst/os-autoinst-needles-opensuse/pull/349

Actions

Copy link

#12