Project

General

Profile

action #67117

[functional][y]test fails in yast2_proxy and yast2_dns_server

Added by syrianidou_sofia over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - SLE 15 SP2
Start date:
2020-05-21
Due date:
2020-06-16
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP2-Online-x86_64-yast2_ncurses_gnome@64bit fails in
yast2_proxy

When needle https://openqa.suse.de/tests/4264234#step/yast2_proxy/9 is matched, the system should choose "Start", verify the selection and then proceed with rest of the module yast2_proxy steps. In the autoinst logs:

[2020-05-21T07:14:41.839 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_after_writing_conf", timeout=1)
[2020-05-21T07:14:41.961 CEST] [debug] >>> testapi::_handle_found_needle: found yast2_proxy-yast2_ncurses_service_start_after_writing_conf-20180827, similarity 1.00 @ 336/320
[2020-05-21T07:14:41.961 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:77 called testapi::send_key
[2020-05-21T07:14:41.962 CEST] [debug] <<< testapi::send_key(key="alt-a", wait_screen_change=0, do_wait=0)
[2020-05-21T07:14:42.297 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:78 called testapi::send_key
[2020-05-21T07:14:42.297 CEST] [debug] <<< testapi::send_key(key="end", do_wait=0, wait_screen_change=0)
[2020-05-21T07:14:42.565 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:79 called testapi::send_key_until_needlematch
[2020-05-21T07:14:42.565 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_on_boot_after_reboot", timeout=1)
[2020-05-21T07:14:42.910 CEST] [debug] no match: 2.7s, best candidate: yast2_proxy-yast2_ncurses_service_start_on_boot_after_reboot-20180827 (0.29)

Looks like the sent keys don't have the expected effect on the test. The worker is looking for the next needle "yast2_ncurses_service_start_on_boot_after_reboot" without actually verifying "yast2_ncurses_service_check_start_after_writing_conf" needle.

In test https://openqa.suse.de/tests/4231081#step/yast2_proxy/10 , where the result is the expected one, the autoinst logs:

[2020-05-13T19:17:44.759 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_after_writing_conf", timeout=1)
[2020-05-13T19:17:44.968 CEST] [debug] >>> testapi::_handle_found_needle: found yast2_proxy-yast2_ncurses_service_start_after_writing_conf-20180827, similarity 1.00 @ 336/320
[2020-05-13T19:17:44.968 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:55 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:81 called testapi::send_key
[2020-05-13T19:17:44.969 CEST] [debug] <<< testapi::send_key(key="ret", do_wait=0, wait_screen_change=0)
[2020-05-13T19:17:45.255 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:55 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:82 called testapi::assert_screen
[2020-05-13T19:17:45.256 CEST] [debug] <<< testapi::assert_screen(mustmatch="yast2_ncurses_service_check_start_after_writing_conf", timeout=30)
[2020-05-13T19:17:45.945 CEST] [debug] >>> testapi::_handle_found_needle: found yast2_proxy-yast2_ncurses_service_check_start_after_writing_conf-20180827, similarity 1.00 @ 454/289
[2020-05-13T19:17:45.945 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:77 called testapi::send_key
[2020-05-13T19:17:45.945 CEST] [debug] <<< testapi::send_key(key="alt-a", wait_screen_change=0, do_wait=0)
[2020-05-13T19:17:46.281 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:78 called testapi::send_key
[2020-05-13T19:17:46.282 CEST] [debug] <<< testapi::send_key(key="end", do_wait=0, wait_screen_change=0)
[2020-05-13T19:17:46.552 CEST] [debug] tests/console/yast2_proxy.pm:90 called yast2_widget_utils::change_service_configuration -> lib/yast2_widget_utils.pm:56 called yast2_widget_utils::change_service_configuration_step -> lib/yast2_widget_utils.pm:79 called testapi::send_key_until_needlematch
[2020-05-13T19:17:46.552 CEST] [debug] <<< testapi::check_screen(mustmatch="yast2_ncurses_service_start_on_boot_after_reboot", timeout=1)
[2020-05-13T19:17:46.879 CEST] [debug] no match: 2.7s, best candidate: yast2_proxy-yast2_ncurses_service_start_on_boot_after_reboot-20180827 (0.29)

looks like after the first needle much, 'ret' should be sent instead of 'alt-a' and 'end' that would be expected after the matching "yast2_proxy-yast2_ncurses_service_check_start_after_writing_conf" .

The issue needs further investigation and possibly, follow up ticket with tools team.

History

#1 Updated by syrianidou_sofia over 1 year ago

The failure on yast2_dns_server module looks similar with the previous failure. Could be due to the same issue.

#2 Updated by riafarov over 1 year ago

  • Due date set to 2020-06-16
  • Priority changed from Normal to High
  • Target version set to SLE 15 SP2

#3 Updated by riafarov over 1 year ago

  • Assignee set to riafarov

This is due to missing EXTRA_TEST setting which we had before.

#4 Updated by riafarov over 1 year ago

  • Status changed from New to Feedback

#5 Updated by riafarov over 1 year ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF