461f3a6132
Summary: This adds some logging related to the update testing workflow, so we have some idea what we actually tested. We log precisely which packages were actually downloaded from the update - this is important as updates can be edited and when examining results we'll want to know which packages actually got used. We also add a new module which runs at the end of postinstall and tries to figure out which packages from the update were installed in the course of the test. This still isn't a guarantee the test actually *tested them* in any way, but it at least means they got installed successfully and didn't interfere with the test. Test Plan: Run the update test workflow, check the logs get uploaded and seem accurate (sometimes some RPM garbage messages wind up in the package log, I'm not too worried about that at present). Run the compose test workflow and check it didn't break. Reviewers: jsedlak Reviewed By: jsedlak Subscribers: tflink Differential Revision: https://phab.qa.fedoraproject.org/D1149
31 lines
922 B
Perl
31 lines
922 B
Perl
use base "installedtest";
|
|
use strict;
|
|
use testapi;
|
|
use utils;
|
|
|
|
sub run {
|
|
my $self = shift;
|
|
# do the 'repo setup' steps, which set up a repo containing the
|
|
# update packages and run 'dnf update'
|
|
$self->root_console(tty=>3);
|
|
repo_setup;
|
|
# upload the log of installed packages which repo_setup created
|
|
# we do this here and not in repo_setup because this is the best
|
|
# place to make sure it happens once and only once per job
|
|
upload_logs "/var/log/updatepkgs.txt";
|
|
# reboot, in case any of the updates need a reboot to apply
|
|
script_run "reboot", 0;
|
|
}
|
|
|
|
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 { fatal => 1 };
|
|
}
|
|
|
|
1;
|
|
|
|
# vim: set sw=4 et:
|