Project

General

Profile

Actions
Copy link

action #47855

closed

[functional][u] test fails in reboot_gnome - catch too many tries of send_key_until_needle_match

Added by szarate about 5 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
mgriessmeier
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 26
Start date:
2019-02-13
Due date:
% Done:

0%

Estimated time:
Difficulty:
easy

Description

Observation

openQA test in scenario sle-12-SP5-Server-DVD-aarch64-lvm-full-encrypt@aarch64 fails in
reboot_gnome

I've seen this test fail some other time (sporadically), simply the SUT doesn't get the key combination, causing the logout dialog not to show

Test suite description

Maintainer: riafarov poo#15926

(crypt-)LVM installations can take longer, especially on non-x86_64 architectures. Test suite creates encrypted lvm partition using expert partitioner and performs installation.

Reproducible

Fails since (at least) Build 0114

Expected result

Last good: 0112 (or more recent)

expected result with failure:

An info box is shown when the test fails, catching the repetitions for the send_key_until_needle_match would do the trick: https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/power_action_utils.pm#L59

Further details

Always latest result in this scenario: latest

Related issues 2 (0 open — 2 closed)

Related to openQA Tests - action #48221: [sle][functional][u] test fails in reboot_gnome - timeout issue for getting into boot menuRejected2019-02-21

Actions
Blocked by openQA Tests - action #43676: [functional][u][sporadic] - test fails in reboot_gnome - Encrypted setups is taking longer in comparison to previous buildsResolvedzluo2018-11-12

Actions
Actions
Copy link
 #1

Updated by okurz about 5 years ago

  • Subject changed from [functional][y][u] test fails in reboot_gnome - catch too many tries of send_key_until_needle_match to [functional][u] test fails in reboot_gnome - catch too many tries of send_key_until_needle_match

I think the module "reboot_gnome" should fall into the sole domain of QSF-u

Actions
Copy link
 #2

Updated by okurz about 5 years ago

  • Related to action #48221: [sle][functional][u] test fails in reboot_gnome - timeout issue for getting into boot menu added
Actions
Copy link
 #3

Updated by okurz about 5 years ago

  • Blocked by action #43676: [functional][u][sporadic] - test fails in reboot_gnome - Encrypted setups is taking longer in comparison to previous builds added
Actions
Copy link
 #4

Updated by okurz about 5 years ago

  • Status changed from Workable to Blocked
  • Assignee set to okurz
Actions
Copy link
 #5

Updated by okurz about 5 years ago

  • Target version changed from Milestone 23 to Milestone 25
Actions
Copy link
 #6

Updated by okurz almost 5 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.

Actions
Copy link
 #7

Updated by mgriessmeier almost 5 years ago

  • Target version changed from Milestone 25 to Milestone 26
Actions
Copy link
 #8

Updated by SLindoMansilla over 4 years ago

  • Status changed from Blocked to Rejected
Actions
Copy link

Also available in: Atom PDF