mirror of
https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git
synced 2024-11-10 17:24:20 +00:00
bacb6f1f7b
Summary: Since we can match on multiple needles, we can drop the loop from console_login and instead do it this way, which is simpler and should work better on ARM (the timeouts will scale and allow ARM to be slow here). Also move it to main_common as there's no logical reason for it to be a class method. Also remove the `check` arg. `check` was only set to 0 by two tests, _console_shutdown and anacondatest's _post_fail_hook. For _console_shutdown, I think I just wanted to give it the best possible chance of succeeding. But we're really not going to lose anything significant by checking, the only case where check=>0 would've helped is if the 'good' needle had stopped matching, and all sorts of other tests will fail in that case. anacondatest was only using it to save a screenshot of whatever was on the tty if it didn't reach a root console, which doesn't seem that useful, and we'll get screenshots from check_screen and assert_screen anyway. Test Plan: Run all tests, check they behave as expected and none inappropriately fails on console login. Reviewers: jskladan, garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D1016
33 lines
1.1 KiB
Perl
33 lines
1.1 KiB
Perl
use base "installedtest";
|
|
use strict;
|
|
use testapi;
|
|
|
|
sub run {
|
|
my $self = shift;
|
|
# this shutdown code is only to make sure the guest disk is clean
|
|
# before uploading an image of it, we're really not "testing"
|
|
# shutdown here. So to keep things simple and reliable, we do not
|
|
# use the desktops' graphical shutdown methods, we just go to a
|
|
# console and run 'poweroff'. We can write separate tests for
|
|
# properly testing shutdown/reboot/log out from desktops.
|
|
$self->root_console(tty=>3);
|
|
script_run("poweroff", 0);
|
|
assert_shutdown;
|
|
}
|
|
|
|
# this is not 'fatal' or 'important' as all wiki test cases are passed
|
|
# even if shutdown fails. we should have a separate test for shutdown/
|
|
# logout/reboot stuff, might need some refactoring.
|
|
sub test_flags {
|
|
# without anything - rollback to 'lastgood' snapshot if failed
|
|
# 'norollback' - don't rollback if failed
|
|
# 'fatal' - whole test suite is in danger if this fails
|
|
# 'milestone' - after this test succeeds, update 'lastgood'
|
|
# 'important' - if this fails, set the overall state to 'fail'
|
|
return {'norollback' => 1};
|
|
}
|
|
|
|
1;
|
|
|
|
# vim: set sw=4 et:
|