Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
tests: use dnf --refresh install to avert stale cache #3721
Conversation
codecov-io
commented
Aug 11, 2017
Codecov Report
@@ Coverage Diff @@
## master #3721 +/- ##
==========================================
- Coverage 75.65% 75.65% -0.01%
==========================================
Files 391 391
Lines 33849 33849
==========================================
- Hits 25609 25608 -1
- Misses 6418 6419 +1
Partials 1822 1822
Continue to review full report at Codecov.
|
zyga
merged commit 506d333
into
snapcore:master
Aug 11, 2017
1 of 7 checks passed
artful-amd64
autopkgtest running
Details
xenial-amd64
autopkgtest running
Details
xenial-i386
autopkgtest running
Details
xenial-ppc64el
autopkgtest running
Details
yakkety-amd64
autopkgtest running
Details
zesty-amd64
autopkgtest running
Details
continuous-integration/travis-ci/pr
The Travis CI build passed
Details
zyga
deleted the
zyga:fix/dnf-install-refresh
branch
Aug 11, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
zyga commentedAug 11, 2017
While our package abstraction helper for spread tests does call dnf
makecache evidence in test failures shows that something is not quite
right and we fail to install packages that have since, in the archive,
been upgraded to a new revision and we attempt to install the old
version oblivious to that fact.
Neal Gompa suggested that we use the --refresh option on dnf install to
always ensure that the package cache is updated if it is out of date.
Signed-off-by: Zygmunt Krynicki zygmunt.krynicki@canonical.com