Merge ~sbeattie/qa-regression-testing:lpci-apply_updates_before_testing into qa-regression-testing:master
Status: | Merged |
---|---|
Merged at revision: | d1402ed74e41ec5d03968e5f0026a28340459397 |
Proposed branch: | ~sbeattie/qa-regression-testing:lpci-apply_updates_before_testing |
Merge into: | qa-regression-testing:master |
Diff against target: |
131 lines (+29/-1) 1 file modified
.launchpad.yaml (+29/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Emilia Torino | Approve | ||
Review via email: mp+465105@code.launchpad.net |
Commit message
lpci: run `apt upgrade` before exercising tests
The automatic runs of qa-regression-
the util-linux tests, even though the most recent util-linux
security update had been published to the ubuntu archive, because
lpci explicitly does not apply updates to the spawned test
environments that the jobs are run in. Furthermore, there is no
specific job configuration to tell lpci to apply updates first in
https:/
To work around this limitation, add a run-before step in each job to run
`apt upgrade` so that the most up-to-date version of a package is tested
against.
An open question here is whether it would be more appropriate to use
`dist-upgrade` rather than a simple `upgrade`
Thanks for fixing this Steve.
I see this might need to be added every time a new job is added, so wondering how to make sure we don't forget. I check but it seems there it seems there is no such "top-level" (not per job) configuration: https:/ /lpci.readthedo cs.io/en/ latest/ configuration. html#top- level-configura tion.