Project

General

Profile

action #45131

[functional][u] test fails in worker to unlock the screen of openQA-in-openQA test

Added by okurz over 4 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
mgriessmeier
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 35+
Start date:
2018-12-13
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install+publish@64bit-2G fails in
worker

Reproducible

Fails since (at least) Build :TW.1874 (current job)

Expected result

Last good: :TW.1873 (or more recent)

Further details

Always latest result in this scenario: latest

Related issues

Related to openQA Tests - action #45710: [functional][u] test fails in NM_wpa2_enterprise - unable to login into the gnome session again (was: screenlock displays)Resolved2019-01-042019-02-08

Related to openQA Tests - action #44153: [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlockRejected2018-11-21

Blocked by openQA Project - action #44441: test fails in dashboard of openQA-in-openQA test, timeout looking for desktop runner is too short, do we have old x11_start_program code in os-autoinst-distri-openQA?New

History

#1 Updated by SLindoMansilla over 4 years ago

  • Subject changed from test fails in worker to unlock the screen of openQA-in-openQA test to [functional][u] test fails in worker to unlock the screen of openQA-in-openQA test

#2 Updated by SLindoMansilla over 4 years ago

  • Target version set to Milestone 24

#3 Updated by okurz over 4 years ago

  • Related to action #45710: [functional][u] test fails in NM_wpa2_enterprise - unable to login into the gnome session again (was: screenlock displays) added

#4 Updated by okurz over 4 years ago

  • Related to action #44153: [functional][u][sporadic] test fails in gnome_control_center - fails to unlock screenlock added

#5 Updated by okurz about 4 years ago

  • Blocked by action #44441: test fails in dashboard of openQA-in-openQA test, timeout looking for desktop runner is too short, do we have old x11_start_program code in os-autoinst-distri-openQA? added

#6 Updated by okurz about 4 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz

#7 Updated by okurz about 4 years ago

  • Target version changed from Milestone 24 to Milestone 25

-> #44441

#8 Updated by okurz about 4 years ago

  • Assignee changed from okurz to mgriessmeier

Move to new QSF-u PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-u. Feel free to discuss with me or reassign to me or someone else in this case. Thanks.

#9 Updated by mgriessmeier almost 4 years ago

  • Target version changed from Milestone 25 to Milestone 26

#10 Updated by mgriessmeier almost 4 years ago

  • Target version changed from Milestone 26 to Milestone 30+

#11 Updated by mgriessmeier over 3 years ago

  • Target version changed from Milestone 30+ to Milestone 35+

#12 Updated by mgriessmeier about 3 years ago

  • Status changed from Blocked to Rejected

works

Also available in: Atom PDF