7687a3aa34
Summary: This has all console tests check for AVCs (with ausearch) and crashes (with coredumpctl) at post-install stage. It's non- fatal as this doesn't really mean the test failed, but we want to spot when there are unexpected AVCs or crashes. Test Plan: Run some console tests, check it works right. I only tested with one test, since so many are broken on Rawhide ATM Reviewers: jskladan, garretraziel Reviewed By: garretraziel Subscribers: tflink Differential Revision: https://phab.qadevel.cloud.fedoraproject.org/D1066
25 lines
722 B
Perl
25 lines
722 B
Perl
use base "installedtest";
|
|
use strict;
|
|
use testapi;
|
|
|
|
sub run {
|
|
my $self = shift;
|
|
$self->root_console(tty=>3);
|
|
# check there are no AVCs. We use ! because this returns 1
|
|
validate_script_output '! ausearch -m avc -ts yesterday 2>&1', sub { $_ =~ m/<no matches>/ };
|
|
# check there are no crashes
|
|
validate_script_output '! coredumpctl list 2>&1', sub { $_ =~ m/No coredumps found/ };
|
|
}
|
|
|
|
sub test_flags {
|
|
# without anything - rollback to 'lastgood' snapshot 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 {};
|
|
}
|
|
|
|
1;
|
|
|
|
# vim: set sw=4 et:
|