Fails to realize the source folder changed with Multipass
Metadata
Current evaluation
Multipass build instance identity uses only the snapcraft.yaml name, so same-named projects in different source folders share one build VM. Acknowledged by sergiusens in 2020; the Multipass provider is absent from today's codebase.
Suggested action: close stale
Reason: The only maintainer response, ~sergiusens (2020-05-19), identifies the root cause and required change: "Projects need to use path to project as an index for this to work, so far we have only used 'name' from snapcraft.yaml" — that change was never made. More importantly, the affected subsystem no longer exists: the supplied repo layout has no snapcraft/providers/ directory (where the legacy Multipass/LXD providers lived), and the current tree is the modern craft-parts/extension-based Snapcraft where the Multipass provider has been removed, making the reported behaviour unreachable. Note: all code-search tools errored out, so I could not grep-verify the removal directly; the directory listing is the only positive evidence.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
12
Quick Win:
3
Complexity:
30
Confidence:
70
Actionability:
40
|
close stale | Multipass build instance identity uses only the snapcraft.yaml name, so same-named projects in different source folders share one build VM. Acknowledged by sergiusens in 2020; the Multipass provider is absent from today's codebase. | |
| stealth/space-bunny-alpha |
Impact:
48
Quick Win:
21
Complexity:
42
Confidence:
79
Actionability:
76
|
keep open | Acknowledged Multipass instance collision: same-named projects in different source directories reuse one build VM because the instance identity does not include the source path. | |
| qwen/qwen3.6-35b-a3b |
Impact:
50
Quick Win:
8
Complexity:
60
Confidence:
40
Actionability:
40
|
keep open | Snapcraft reuses Multipass instances when building the same project from different folders, failing to detect source folder changes. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
24
Staleness:
95
Complexity:
40
Confidence:
50
Support Request:
10
|
close stale | Bug where building the same project from different source folders reuses the previous Multipass instance instead of creating a new one. 6+ years old with zero comments, no labels, and no maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
85
Support Request:
10
|
close stale | Reports Multipass instance reuse across different source folders instead of separate builds. Unlabeled, no maintainer response, and inactive for over 6 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
55
Confidence:
90
Support Request:
10
|
close stale | Bug where Multipass build instances are incorrectly reused across different source directories instead of being isolated per directory. Issue is extremely stale with no maintainer engagement or activity in over six years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
10
|
close stale | Bug report about Multipass instance caching incorrectly reusing a VM across different source directories. Issue is over 6 years old with no maintainer response or comments. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
multipass#1452
(confidence 95%)
Explicitly cited in the issue body as the original report; the instance-collision problem was filed on the Multipass tracker and mirrored to Launchpad.
Related issues
No related issues found above the similarity threshold.