Project

General

Profile

Actions

action #17446

closed

[qam][x11regressions]test fails in evince_find sporadically (network issue or mistyping on long strings)

Added by pgeorgiadis about 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2017-03-02
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP2-Desktop-DVD-Updates-x86_64-qam-regression-documentation@64bit fails in
evince_find

Reproducible

Fails since (at least) Build 20170301-1
also failed 22 times in maintenance for the past 3 months, but in different steps. It seems quite untrustworthy test.

Expected result

Last good: 20170228-6 (or more recent)
See expected step 2

Further details

Always latest result in this scenario: latest

I couldn't find any valuable information in the logs, but it's pretty clear from the screenshots that it couldn't load the file from the network. It either a network issue, it's a race condition.

logs from the problem:

<<< testapi::type_string(string='evince http://10.160.1.100:20013/LkWEMPopELuqXtxg/data/x11regressions/test.pdf', max_interval=250, wait_screen_changes=0)
susedistribution::x11_start_program('susedistribution=HASH(0x3b75298)', 'evince http://10.160.1.100:20013/LkWEMPopELuqXtxg/data/x11reg...', undef, undef) called at /usr/lib/os-autoinst/testapi.pm line 690
testapi::x11_start_program('evince http://10.160.1.100:20013/LkWEMPopELuqXtxg/data/x11reg...') called at /var/lib/openqa/share/tests/sle/tests/x11regressions/evince/evince_find.pm line 21
evince_find::run('evince_find=HASH(0x4b31d20)') called at /usr/lib/os-autoinst/basetest.pm line 306
eval {...} called at /usr/lib/os-autoinst/basetest.pm line 304
basetest::runtest('evince_find=HASH(0x4b31d20)') called at /usr/lib/os-autoinst/autotest.pm line 244

logs from passed:

<<< testapi::type_string(string='evince http://10.160.1.100:20083/WN4dmcE9jbV7FmMs/data/x11regressions/test.pdf', max_interval=250, wait_screen_changes=0)
susedistribution::x11_start_program('susedistribution=HASH(0x50365a8)', 'evince http://10.160.1.100:20083/WN4dmcE9jbV7FmMs/data/x11reg...', undef, undef) called at /usr/lib/os-autoinst/testapi.pm line 690
testapi::x11_start_program('evince http://10.160.1.100:20083/WN4dmcE9jbV7FmMs/data/x11reg...') called at /var/lib/openqa/share/tests/sle/tests/x11regressions/evince/evince_find.pm line 21
evince_find::run('evince_find=HASH(0x6009ba0)') called at /usr/lib/os-autoinst/basetest.pm line 306
eval {...} called at /usr/lib/os-autoinst/basetest.pm line 304
basetest::runtest('evince_find=HASH(0x6009ba0)') called at /usr/lib/os-autoinst/autotest.pm line 244

Related issues 1 (0 open1 closed)

Has duplicate openQA Project - action #17442: [tools]Bad performance or too many failures because of typing too soon/mistyping (send_keys/type_string)ResolvedRBrownSUSE2017-03-02

Actions
Actions #1

Updated by okurz about 7 years ago

  • Subject changed from test fails in evince_find to [qam]test fails in evince_find sporadically (network issue or mistyping on long strings)
Actions #2

Updated by okurz about 7 years ago

  • Subject changed from [qam]test fails in evince_find sporadically (network issue or mistyping on long strings) to [qam][x11regressions]test fails in evince_find sporadically (network issue or mistyping on long strings)
Actions #3

Updated by mitiao about 7 years ago

  • Assignee changed from mitiao to qkzhu

Discussed with Qingkai and re-assign it to him.
I am busy on migration stuffs, sorry and thanks.

Actions #4

Updated by qkzhu about 7 years ago

  • Has duplicate action #17442: [tools]Bad performance or too many failures because of typing too soon/mistyping (send_keys/type_string) added
Actions #5

Updated by qkzhu about 7 years ago

  • Status changed from New to In Progress

It didn't fail in the last 50 history: https://openqa.suse.de/tests/865996?arch=x86_64&test=qam-regression-documentation&limit_previous=50&version=12-SP2&machine=64bit&flavor=Desktop-DVD-Updates&distri=sle#previous

I think this issue was caused by poo#17442 (Bad performance or too many failures because of typing too soon/mistyping) which was fixed now.

Actions #6

Updated by qkzhu about 7 years ago

  • Status changed from In Progress to Resolved

Pleas feel free to reopen it if this occurs again.

Actions

Also available in: Atom PDF