Project

General

Profile

Actions

action #19268

closed

[tools][aarch64] test fails in yast2_lan_restart: missing keys in assert_script_run with aarch64

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

Status:
Resolved
Priority:
Normal
Category:
Infrastructure
Target version:
-
Start date:
2017-05-19
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

Ninja keys appeared for aarch64 : https://openqa.suse.de/tests/942993#step/yast2_lan_restart/309 in assert_script_run method.
After assert_script_run 'dig suse.com|grep \'status: NOERROR\''; call, "." is missing in the console.

Autoinst log in the attachment
openQA test in scenario sle-12-SP3-Server-DVD-aarch64-extra_tests_on_gnome@aarch64 fails in
yast2_lan_restart

Reproducible

Fails since (at least) Build 0389
Sporadic issue. It did not happened again on OSD since the last 10 builds.

Expected result

Last good: Build [0387] https://openqa.suse.de/tests/940145

Further details

Always latest result in this scenario: latest

Workaround

Restart the job.


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #19778: [sle][functional][aarch64] test fails in updates_packagekit_gpk due to doubled keyRejected2017-06-13

Actions
Actions #1

Updated by okurz almost 7 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: extra_tests_on_gnome
https://openqa.suse.de/tests/979332

Actions #2

Updated by riafarov almost 7 years ago

Please, ignore automated as issue is sporadic and job fails due to another reason. Removed label from job comments as is misleading.

Actions #3

Updated by riafarov almost 7 years ago

  • Related to action #19778: [sle][functional][aarch64] test fails in updates_packagekit_gpk due to doubled key added
Actions #4

Updated by SLindoMansilla almost 7 years ago

  • Status changed from New to In Progress
  • Assignee set to SLindoMansilla
Actions #5

Updated by SLindoMansilla almost 7 years ago

  • Description updated (diff)
  • Status changed from In Progress to Feedback
  • Priority changed from High to Normal

There is nothing in the test that I can improve. The only solution would be to slow down the type speed. But since it is a very sporadic issue, I would simply suggest as a Workaround restarting the job.
In case that this issue arise again and often, the speed of the typing should be slow down.

Actions #6

Updated by SLindoMansilla over 6 years ago

Verification on OSD about backend problem with missing needles.

No more missing keys on that since 3 months: osd#last_400

Actions #7

Updated by SLindoMansilla over 6 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF