This repository has been archived by the owner on Oct 4, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch allows spread tests to work offline. It requires some
explicit setup that is described in spread-tests/offline-content/README
The main motivator for this change is that it makes the testing cycle
work while on the plane/bus/train or where connectivity is limited or
unreliable. Even with reliable conncetion it can cut test time
significantly. On my relatively slow machine a full spread run for
xenial can now run in roughly 9 minutes. As a comparison, the same tests
ran on linode for nearly 11 minutes. I don't have hard numbers for
online tests on my machine (offline also makes some expensive operations
cached) but the initial time was closer to 20 minutes.
As a secondary factor testing is now a little bit more reproducible and
repatable. Spread makes ordering non-deterministic but at least package
building and snap revisions are fixed.
Signed-off-by: Zygmunt Krynicki zygmunt.krynicki@canonical.com