Avoid unconditional wait for Timbuktu screen in _boot_to_anaconda
The way this currently works, the test unconditionally waits 60 seconds for the "Timbuktu screen" (the warning dialog shown on pre-release images) to appear when anaconda is starting up, even if it's testing an image where it doesn't show up. Now we test Atomic nightlies and live respins and stuff this happens quite a lot, so let's avoid it. This way if the hub appears during those 60 seconds we'll spot it right away and continue, otherwise we behave the same as before. Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
parent
05c9f4fbcd
commit
06fbeca281
@ -62,11 +62,22 @@ sub run {
|
|||||||
assert_screen "anaconda_select_install_lang_selected", 3;
|
assert_screen "anaconda_select_install_lang_selected", 3;
|
||||||
assert_and_click "anaconda_select_install_lang_continue";
|
assert_and_click "anaconda_select_install_lang_continue";
|
||||||
|
|
||||||
if ( check_screen "anaconda_rawhide_accept_fate", 60 ) {
|
# wait 60 secs for hub or Rawhide warning dialog to appear.
|
||||||
assert_and_click "anaconda_rawhide_accept_fate";
|
# If the hub appears, return - we're done now. If Rawhide
|
||||||
|
# warning dialog appears, accept it.
|
||||||
|
if (check_screen ["anaconda_rawhide_accept_fate", "anaconda_main_hub"], 60) {
|
||||||
|
if (match_has_tag("anaconda_rawhide_accept_fate")) {
|
||||||
|
assert_and_click "anaconda_rawhide_accept_fate";
|
||||||
|
}
|
||||||
|
else {
|
||||||
|
# this is when the hub appeared already, we're done
|
||||||
|
return;
|
||||||
|
}
|
||||||
}
|
}
|
||||||
|
# This is where we get to if we accepted fate above, *or*
|
||||||
# wait for Anaconda hub to appear
|
# didn't match anything: if the Rawhide warning didn't
|
||||||
|
# show by now it never will, so we'll just wait for the
|
||||||
|
# hub to show up.
|
||||||
assert_screen "anaconda_main_hub", 900; #
|
assert_screen "anaconda_main_hub", 900; #
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
Loading…
Reference in New Issue
Block a user