Project

General

Profile

Actions
Copy link

action #58586

closed

[functional][u] test fails in yast2_bootloader - wrong assert_screen and timeout too small for aarch64

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

Status:
Resolved
Priority:
Normal
Assignee:
szarate
Category:
Bugs in existing tests
Target version:
SUSE QA (private) - Milestone 28
Start date:
2019-10-23
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

While usually this test module passes, it could fail due to the short timeout of 200 and a assert_screen call, that could cause an early failure if mkinitrd is not finished yet.

openQA test in scenario sle-12-SP5-Server-DVD-aarch64-wsm+sdk+textmode@aarch64 fails in
yast2_bootloader

Test suite description

Maintainer: dheidler - Run php tests for Web Scripting Module,
same as wsm+dev_tools+textmode, but uses SDK addon instead of Development tools module.

Reproducible

Fails since (at least) Build 0368 (current job)

Expected result

Last good: 0366 (or more recent)

Further details

Always latest result in this scenario: latest

Related issues 1 (0 open — 1 closed)

Related to openQA Tests (public) - action #56651: [functional][u][sporadic] test fails in vim - yast2-booloader left visual artifactResolveddheidler2019-09-09

Actions
Actions
Copy link
 #1

Updated by okurz about 5 years ago

  • Related to action #56651: [functional][u][sporadic] test fails in vim - yast2-booloader left visual artifact added
Actions
Copy link
 #2

Updated by szarate about 5 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link

Also available in: Atom PDF