764c6dbd95
We hit an interesting case in update testing recently: https://bodhi.fedoraproject.org/updates/FEDORA-2018-115068f60e An earlier version of that update failed testing. When we dug into it a bit, we found that the test was failing because an earlier version of the `pki-server` package was installed than the version that was in the update; when asked (as part of FreeIPA deployment) to install it, dnf had noticed that there were dependency issues with the version of the package from the update, but it happened to be able to install the version from the frozen 'stable' repo...so it just went ahead and did that. In this case, the 'missed' package resulted in a test failure, but it'd actually be possible for this to happen and the test to complete; we really ought to notice when this happens, and treat it as a test failure. So what this attempts to do is: at the end of all update tests, check for all installed packages with the same name as a package from the update, and compare their full NEVR to the one of the package from the update. If a package with the same name as one of the update packages is installed, but does not appear to be the *same NEVR*, we fail, and upload the lists of packages for manual investigation as to what the heck's going on. Signed-off-by: Adam Williamson <awilliam@redhat.com> |
||
---|---|---|
.. | ||
anaconda.pm | ||
anacondatest.pm | ||
fedoradistribution.pm | ||
freeipa.pm | ||
installedtest.pm | ||
packagetest.pm | ||
tapnet.pm | ||
utils.pm |