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 |
||
|---|---|---|
| .. | ||
| anaconda.pm | ||
| anacondatest.pm | ||
| fedoradistribution.pm | ||
| freeipa.pm | ||
| installedtest.pm | ||
| packagetest.pm | ||
| tapnet.pm | ||
| utils.pm | ||