Snapcraft spread tests should be tested with every provider
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Spread tests run inconsistently across LXD and Multipass providers due to differing base image contents. Suggests running tests on all providers to ensure compatibility. Currently untriaged and inactive for nearly 3 years.
Suggested action: close stale
Reason: The issue is nearly three years old with zero maintainer interaction. Snapcraft's test infrastructure and base image standards have likely evolved significantly since then, making the original request outdated or already addressed. High confidence in closing due to extreme inactivity and lack of current relevance.
Staleness:
95
Complexity:
40
Confidence:
90
Support Request:
10
Issue body
Most spread tests are currently running in destructive mode.
The problem is that the content of the base lxd image and multipass images are different.
As an example for core18, the lxd image doesn't have the package distro-info-data while the multipass image contains it.
This can cause inconsistencies when building a snap with different providers.
Snapcraft spread tests (or integration tests in general) should be running in every provider to ensure that the example snaps are working fine independently of the provider that was selected by the user.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
90
Support Request:
10
|
close stale | Spread tests run inconsistently across LXD and Multipass providers due to differing base image contents. Suggests running tests on all providers to ensure compatibility. Currently untriaged and inactive for nearly 3 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
45
Confidence:
85
Support Request:
10
|
close stale | Technical request to run Snapcraft spread tests across all providers to prevent image inconsistencies. Unlabelled, zero comments, inactive for over three years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
55
Confidence:
85
Support Request:
5
|
close stale | Feature request to run Spread tests across all providers to avoid image inconsistencies. Unlabelled, zero comments, inactive for nearly three years. Core18 is EOL. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
60
Confidence:
75
Support Request:
10
|
needs triage | Proposal to run Snapcraft spread tests across all providers to prevent build inconsistencies from differing base images. Currently untriaged and inactive for nearly three years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2509 Investigation: Spread test failures are due to craft_providers snapd initialization issue | charmcraft | open | Documentation-only PR adding craft-providers-bug-report.md about spread test failures from a snapd socket-activation race in LXD containers. Inactive ~8.5 months; the recommended retry fix was merged upstream in craft-providers. |