spread: only run in LXD with the google/multipass provider for repo
Metadata
Current evaluation
Merged #3120, limiting repo Spread runs to LXD with the google/multipass provider and using --destructive-mode in autopkgtest pending environment verification.
Resolution: closed resolved
Reason: PR snapcraft#3120 was approved and merged with no unresolved review comments. It implemented the proposed test-environment restrictions and temporary destructive-mode workaround.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Use --destructive-mode for testing in autopkgtest until the
environment is verified to work.
Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com>
- [ ] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `./runtests.sh static`?
- [ ] Have you successfully run `./runtests.sh tests/unit`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #3120, limiting repo Spread runs to LXD with the google/multipass provider and using --destructive-mode in autopkgtest pending environment verification. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #3120 restricted the repository spread suite to LXD with the google/multipass provider and temporarily enabled autopkgtest destructive mode (commit 20b297b0f). | |
| qwen/qwen3.6-35b-a3b | — | — | Merged changes restricting spread tests to LXD with the google/multipass provider for the repo. Switched autopkgtest to destructive mode to bypass dirmngr failures until the environment is verified. Approved and passed CI. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged changes to restrict spread tests to LXD with google/multipass providers. Switched to --destructive-mode for autopkgtest to bypass dirmngr failures in LXD until the environment is verified. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2631 spread tests: enable LXD build provider tests | snapcraft | merged | Merged PR #2631 enabled LXD build-provider spread tests and reused early-prepared LXD setup, reducing repeated setup and image-download overhead. | |
| #467 test(spread): use LXD provider for spread tests | imagecraft | closed | PR closed without merge; spread LXD provider changes were implemented across follow-up PRs (#483, #485, #486, #487, #488, #495) | |
| #2983 tests: add LXD spread test | snapcraft | merged | Merged PR #2983 as 4b8522a14, adding spread coverage that builds the LXD package with LXD and destructive/host providers; installation checks were deferred. | |
| #2682 tests: change default spread provider to lxd outside of travis | snapcraft | merged | Merged PR #2682 (commit 8b41444a3) refactored runtests.sh, defaulted Spread to LXD outside Travis, and configured Travis to use google:. | |
| #487 test(spread): run the simple pack test in all providers | imagecraft | merged | Merged PR #487 adds variants of the simple pack test to run across LXD, multipass, and host/destructive providers, fixing #480. | |
| #1225 tests: improve multipass spread backend | charmcraft | merged | Merged as 6d68140c, adding concurrent Multipass Spread workers with LXD-style naming; defaults use 2 workers for Ubuntu 22.04 and 1 for other series. | |
| #302 test(spread): switch to testing in destructive mode | imagecraft | merged | Merged PR #302 as commit f6aae5e, switching spread tests to destructive mode while LXD lacks required loop-device support. | |
| #2937 spread tests: do not attempt to remove snapd snap | snapcraft | merged | Merged in commit b9290bb32; spread tests now skip removing the protected snapd snap, fixing LXD test failures. |