Project

General

Profile

Actions

action #38270

closed

[functional][y][sporadic][aarch64] test fails in yast2_i - missing keys while searching for a package name

Added by oorlov almost 6 years ago. Updated about 5 years ago.

Status:
Rejected
Priority:
Low
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2018-07-06
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP4-Server-DVD-aarch64-allpatterns@aarch64 fails in
yast2_i

The test searches for a 'yast2-nfs-client', then removes all the characters by iterating a loop for (1 .. length($pkgname)) { send_key "backspace" }.

But in the current build it is failed because it removed several characters and then missed keys (probably because of some slowness of the system).

Suggestion

Use send_key_until_needlematch method instead of just looping for the exact number of characters in the package name.

Reproducible

Fails since (at least) Build 0245

Expected result

Last good: 0243 (or more recent)

Further details

Always latest result in this scenario: latest

Workaround


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #39011: [functional] Low performance on openqa production serverResolvedokurz2018-08-01

Actions
Actions #1

Updated by oorlov almost 6 years ago

  • Subject changed from test fails in yast2_i to test fails in yast2_i - missing keys while searching for a package name
Actions #2

Updated by oorlov almost 6 years ago

  • Subject changed from test fails in yast2_i - missing keys while searching for a package name to [functional][y][sporadic]test fails in yast2_i - missing keys while searching for a package name
Actions #3

Updated by oorlov almost 6 years ago

  • Description updated (diff)
Actions #4

Updated by oorlov almost 6 years ago

  • Subject changed from [functional][y][sporadic]test fails in yast2_i - missing keys while searching for a package name to [functional][y][sporadic][aarch64] test fails in yast2_i - missing keys while searching for a package name
Actions #5

Updated by okurz almost 6 years ago

  • Target version set to future
Actions #6

Updated by okurz almost 6 years ago

  • Description updated (diff)
  • Priority changed from Normal to Low

Interesting case. If found again we should prioritize higher. Please mention subsequent failures here but retrigger the failed jobs.

Actions #7

Updated by okurz over 5 years ago

  • Related to action #39011: [functional] Low performance on openqa production server added
Actions #8

Updated by riafarov about 5 years ago

  • Status changed from New to Rejected
  • Assignee set to riafarov

Same as for #38294, both issues occurred at the same timeframe. Nothing to be addressed atm.

Actions

Also available in: Atom PDF