action #13710
closed
action #10558: improve yast2_lan test robustness
yast2_lan fails on script_sudo matching previous password prompt
Added by mkravec over 8 years ago.
Updated over 8 years ago.
Description
yast2_lan matches password prompt from previous steps
Problem:
- assert_script_sudo "zypper -n in yast2-network"
- password prompt matched & password typed
- script_sudo("/sbin/yast2 lan; echo yast2-lan-status-\$? > /dev/$serialdev", 0);
- password prompt from step #1 is matched & password typed
- password for step #2 is available, but password was already typed
https://openqa.suse.de/tests/558658#step/yast2_lan/9
- Parent task set to #10558
- Status changed from New to In Progress
- % Done changed from 0 to 100
- Status changed from In Progress to Resolved
- 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?
- Status changed from In Progress to Resolved
Also available in: Atom
PDF