Spread multipass tests
Metadata
Current evaluation
Merged #3966 as f787c56fe, moving manual Multipass Spread tests out of the legacy test directory while noting they cannot run on Google infrastructure.
Resolution: closed resolved
Reason: PR #3966 was approved and merged into main as f787c56fe, relocating the manual Multipass tests. The maintainer confirmed the Spread failure was unrelated and was resolved separately by #3962.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [X] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [X] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [X] Have you successfully run `make lint`?
- [X] Have you successfully run `pytest tests/unit`?
-----
Move manual multipass tests out of the legacy directory.
It's not a very meaningful PR, since they are manual tests that don't work on the google spread infrastructure, but this PR is still a tiny improvement.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #3966 as f787c56fe, moving manual Multipass Spread tests out of the legacy test directory while noting they cannot run on Google infrastructure. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #3966 as f787c56fe, moving manual Multipass tests from the legacy test directory into Spread. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #3966 as f787c56fe, moving manual Multipass tests from the legacy test directory into Spread. The reported spread failure was unrelated and resolved by #3962. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged #3966 (7ac279b), moving manual multipass tests out of the legacy directory. The unrelated spread failure was fixed separately in #3962. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged a minor refactor moving manual multipass tests out of the legacy directory. An unrelated spread test failure was noted and resolved by a separate pull request. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged. Relocated manual multipass tests from the legacy directory. The associated spread test failure was unrelated and fixed in PR #3962. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcore/snapcraft#3962
(confidence 99%)
Merged as 6122e30fd; it fixed the unrelated snapcraft_legacy container setup failure.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2491 Fix multipass error handling spread test | snapcraft | merged | Merged #2491 in commit 51f8b6191, fixing multipass error-handling spread coverage while retaining the manual switch because gcloud-backed multipass tests were unstable. | |
| #2367 tests: add spread test exercising multipass build VMs | snapcraft | merged | Merged #2367 in commit ad5484896, adding Multipass build-VM Spread coverage and moving amd64 Xenial/Bionic tests to GCE with nested KVM; resolved LP #1798682. | |
| #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. | |
| #4248 spread: separate legacy tests | snapcraft | closed | PR #4248 was merged into main, separating legacy spread tests into dedicated GitHub Actions runs to reduce repeated test execution after failures. | |
| #2979 tests: add multipass adhoc spread backend | snapcraft | merged | Merged PR #2979 (commit d5097a505) adds an adhoc multipass backend to spread.yaml, enabling local spread tests needing containers/snap installs. Backend still present in spread.yaml. | |
| #4571 test: fix spread multipass backend | snapcraft | merged | Merged #4571 as af14c71da, updating Spread’s Multipass backend to use SSH passwords with newer sshd and support multiple workers. | |
| #4247 spread: separate legacy tests | snapcraft | closed | Closed PR #4247 was superseded by merged PR #4248, which split legacy spread tests into separate GitHub Actions runs to reduce repeated work after failures. |