The ubuntu-image that we are installing in the docker test images is
apparently too old to accept it. Probably the issue is that
xenial-updates is not included in the sources.
We avoid contamination from older test runs. Also, creating a new image
is actually quite cheap in time. We also deprecate the --force-new-image
option.
Previously, the --snap option of the tests scripts meant adding an
installed snap to a newly created image. This was not used anywhere
(there was a bug that prevented it from working). Change the meaning so
what it does is copying around a snap file that can be installed
manually later by the spread tests. This way we avoid having to build
the snap inside the VM by using the classic snap.
905f74d...
by
System Enablement CI Bot <email address hidden>
Author: Alfonso Sanchez-Beato <email address hidden>
Search writable partition from kpartx output
Using findfs was not reliable if there were other images (for which
kpartx had created the loop devices) containing that partition. Docker
was leaking these devices into the testing container, which was causing
failures. The devices came from containers in a bad state.
