Our current autopkgtest setup reuses the spread.yaml that we use
for regular spread runs. The regular spread.yaml will modify the
host heavily which is not what we want for the autopkgtest
tests. Here the idea is to use the binaries that got build as
part of the distro build and run a smoke test against the
most pristine system possible.
After poking in {prepare-restore,prepare,reset}.sh I think we
need something radically simpler: a minimal spread.yaml that
is just there for autopkgtest. This PR goes this way.
The downside of this approach is of couse that thing may
get out of sync between the main spread.yaml and the autopkgtest
spread.yaml. To fix this we need a test that runs the autopkgtest
regularly against a clean environment (probably in the nested
suite).
overlord: mock store to avoid net requests (#6945)
* overlord: mock store to avoid net requests
The patch itself is from Samuele, this prevents the unit tests from
hitting the snapcraft web APIs. In certain environments unit tests run
without any network and using anything but local services is disallowed.
Signed-off-by: Zygmunt Krynicki <email address hidden>
* overlord: update managers_test.go after refactor
Co-Authored-By: Zygmunt Krynicki <email address hidden>
Our current autopkgtest setup reuses the spread.yaml that we use
for regular spread runs. The regular spread.yaml will modify the
host heavily which is not what we want for the autopkgtest
tests. Here the idea is to use the binaries that got build as
part of the distro build and run a smoke test against the
most pristine system possible.
After poking in {prepare-restore,prepare,reset}.sh I think we
need something radically simpler: a minimal spread.yaml that
is just there for autopkgtest. This PR goes this way.
The downside of this approach is of couse that thing may
get out of sync between the main spread.yaml and the autopkgtest
spread.yaml. To fix this we need a test that runs the autopkgtest
regularly against a clean environment (probably in the nested
suite).
interfaces: add missing adjtimex to time-control (#6943)
This came up during snapping "chrony" - apparently we do not allow
adjtimex in time-control but its used by chrony and I see no reason
not to add it. Hence this PR :)
interfaces/docker-support: add uc overlafys snippet if privileged too
The privileged attribute doesn't actually imply unconfined, so we still
want to add the Ubuntu Core specific overlayfs snippet if privileged is
connected as well.
