Project

General

Profile

action #36841

[sle12sp4][desktop] test fails in vino_client

Added by qkzhu about 3 years ago. Updated 27 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2018-06-06
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP4-Desktop-DVD-x86_64-remote-desktop-vino-server@64bit fails in
vino_server

This case is blocked by the lock screen, we didn't met this issue in SP3.

History

#1 Updated by okurz about 3 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: remote-desktop-vino-client
https://openqa.suse.de/tests/1770984

#2 Updated by yfjiang about 3 years ago

  • Assignee set to GraceWang

In the failed case, it looks the screenshot of desktop clock next to the failed needle check was 13:47,
while the lock screen shows 13:56, maybe the 11 mins gap caused the screen lock?

#3 Updated by okurz about 3 years ago

Sure, but that is not the root cause. The logs tell:

[2018-06-05T17:49:48.0812 CEST] [debug] MATCH(vino_server-gcc-sharing-activate-20170406:1.00)
[2018-06-05T17:49:48.0903 CEST] [debug] >>> testapi::_handle_found_needle: found vino_server-gcc-sharing-activate-20170406, similarity 1.00 @ 286/233
[2018-06-05T17:49:48.0903 CEST] [debug] mutex create 'vino_server_ready'
[2018-06-05T17:49:48.0986 CEST] [debug] Waiting for 1 jobs to finish
…
[2018-06-05T17:59:09.0514 CEST] [debug] Waiting for 0 jobs to finish
[2018-06-05T17:59:09.0514 CEST] [debug] /var/lib/openqa/cache/tests/sle/tests/x11/remote_desktop/vino_server.pm:61 called testapi::wait_screen_change
[2018-06-05T17:59:09.0514 CEST] [debug] <<< testapi::wait_screen_change(timeout=10, similarity_level=50)

So the server scenario just waits 10 minutes for the client to release the mutex. I would assume the problem is rather on the corresponding client job side but I don't know in detail which is the problem.

#4 Updated by okurz about 3 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: remote-desktop-vino-client
https://openqa.suse.de/tests/1816313

#5 Updated by okurz about 3 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: remote-desktop-vino-client
https://openqa.suse.de/tests/1864401

#6 Updated by GraceWang about 3 years ago

The test suites "remote-desktop-vino-client" and "remote-desktop-vino-server" passed on build0269.
See:
remote-desktop-vino-server: https://openqa.suse.de/tests/1876523#
remote-desktop-vino-client: https://openqa.suse.de/tests/1876528#

I didn't do any change with the two test suites.
And from the latest failed log on build0272 we can see:

[2018-08-01T09:35:09.0677 CEST] [debug] MATCH(vino_client-vinagre-auth-20170406:1.00)
[2018-08-01T09:35:09.0768 CEST] [debug] >>> testapi::_handle_found_needle: found vino_client-vinagre-auth-20170406, similarity 1.00 @ 366/258
[2018-08-01T09:35:09.0768 CEST] [debug] /var/lib/openqa/cache/tests/sle/tests/x11/remote_desktop/vino_client.pm:50 called testapi::type_password
[2018-08-01T09:35:09.0768 CEST] [debug] <<< testapi::type_string(string='SECRET STRING', max_interval=100, wait_screen_changes=0, wait_still_screen=0)
BYTES {"json_cmd_token":"InccxUJY","type_string":{"json_cmd_token":"IwaPuIkD","max_interval":100,"text":"nots3cr3t"}}
[2018-08-01T09:35:10.0891 CEST] [debug] /var/lib/openqa/cache/tests/sle/tests/x11/remote_desktop/vino_client.pm:51 called testapi::wait_still_screen
[2018-08-01T09:35:10.0891 CEST] [debug] <<< testapi::wait_still_screen(similarity_level=47, timeout=30, stilltime=3)
BYTES {"set_reference_screenshot":{"json_cmd_token":"oDncOBfQ"},"json_cmd_token":"ikFvobHX"}
BYTES {"similiarity_to_reference":{"json_cmd_token":"lZoESOwt"},"json_cmd_token":"StAwvJNX"}
BYTES {"json_cmd_token":"VJuwhbDJ","similiarity_to_reference":{"json_cmd_token":"nVrIoqPs"}}
BYTES {"json_cmd_token":"BLOiFJGy","set_reference_screenshot":{"json_cmd_token":"jnYtdPGD"}}
BYTES {"json_cmd_token":"Gyxunikf","similiarity_to_reference":{"json_cmd_token":"dIkTmsCd"}}
BYTES {"json_cmd_token":"CyliQCeI","similiarity_to_reference":{"json_cmd_token":"ihxXNrAq"}}
BYTES {"json_cmd_token":"hvJpQgDD","similiarity_to_reference":{"json_cmd_token":"YUnFcnPM"}}
BYTES {"json_cmd_token":"TKGiKATa","similiarity_to_reference":{"json_cmd_token":"McFSlxrw"}}
BYTES {"json_cmd_token":"btkCfvlT","similiarity_to_reference":{"json_cmd_token":"HaXsAMsl"}}
BYTES {"similiarity_to_reference":{"json_cmd_token":"YjLkbxCW"},"json_cmd_token":"qVHQaxOn"}
[2018-08-01T09:35:14.0429 CEST] [debug] >>> testapi::wait_still_screen: detected same image for 3 seconds
[2018-08-01T09:35:14.0429 CEST] [debug] /var/lib/openqa/cache/tests/sle/tests/x11/remote_desktop/vino_client.pm:52 called testapi::send_key
[2018-08-01T09:35:14.0429 CEST] [debug] <<< testapi::send_key(key='ret', do_wait=0)
BYTES {"json_cmd_token":"AWSPUvms","send_key":{"key":"ret","json_cmd_token":"sEfGjDzO"}}
[2018-08-01T09:35:14.0634 CEST] [debug] /var/lib/openqa/cache/tests/sle/tests/x11/remote_desktop/vino_client.pm:53 called testapi::assert_screen
[2018-08-01T09:35:14.0635 CEST] [debug] <<< testapi::assert_screen(mustmatch='vinagre-gcc-sharing-activate', timeout=30)
BYTES {"json_cmd_token":"oPLkPtwV","check_screen":"vinagre-gcc-sharing-activate"}

When doing assert_screen 'vinagre-gcc-sharing-activate', it returned timeout error.

From the above, I think this might be a performance issue.
I recommend to use a value greater than the default timeout.
Anyway, I will try this on my local machine and see it it works.

#7 Updated by GraceWang almost 3 years ago

  • Subject changed from [sle12sp4][desktop] test fails in vino_server to [sle12sp4][desktop] test fails in vino_client

#8 Updated by okurz almost 3 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: remote-desktop-vino-client
https://openqa.suse.de/tests/1953885

#9 Updated by okurz almost 3 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: remote-desktop-vino-client
https://openqa.suse.de/tests/2023318

#10 Updated by okurz almost 3 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: remote-desktop-vino-client
https://openqa.suse.de/tests/2067902

#11 Updated by okurz almost 3 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: remote-desktop-vino-client
https://openqa.suse.de/tests/2118358

#12 Updated by okurz almost 3 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: remote-desktop-vino-client
https://openqa.suse.de/tests/2177333

#13 Updated by okurz almost 3 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: remote-desktop-vino-client
https://openqa.suse.de/tests/2230040

#14 Updated by GraceWang 27 days ago

  • Status changed from New to Resolved

Also available in: Atom PDF