Project

General

Profile

action #13710

action #10558: improve yast2_lan test robustness

yast2_lan fails on script_sudo matching previous password prompt

Added by mkravec about 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
2016-09-13
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

yast2_lan matches password prompt from previous steps

Problem:

  1. assert_script_sudo "zypper -n in yast2-network"
  2. password prompt matched & password typed
  3. script_sudo("/sbin/yast2 lan; echo yast2-lan-status-\$? > /dev/$serialdev", 0);
  4. password prompt from step #1 is matched & password typed
  5. password for step #2 is available, but password was already typed

https://openqa.suse.de/tests/558658#step/yast2_lan/9

History

#1 Updated by mkravec about 6 years ago

  • Parent task set to #10558

#2 Updated by mkravec about 6 years ago

  • Assignee set to mkravec

#3 Updated by mkravec about 6 years ago

  • Status changed from New to In Progress

#5 Updated by mkravec about 6 years ago

  • Status changed from In Progress to Resolved

#6 Updated by okurz about 6 years ago

  • Status changed from Resolved to In Progress

the explicit script_run now has another problem: https://openqa.opensuse.org/tests/265596#step/prepare_system_for_update_tests/4

I guess $self->script_run("clear"); in lib/susedistribution.pm is a bit too much "high level code" in this distribution implementation of script_sudo. Maybe just using $self->script_run("clear", 0); helps because it just types the clear with a following ret key but as two indidvidual commands to give enough time to execute but not rely on the serialdev, can you check?

#7 Updated by mkravec about 6 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF