bumping the compatibility tag should be more robust
Metadata
Current evaluation
Tests still hardcode buildd-base-v7 while production derives it from Base.compatibility_tag, leaving compatibility-tag bumps vulnerable to inconsistent test updates.
Suggested action: keep open
Reason: The maintainer-authored issue is labeled Type: Enhancement and identifies a concrete recurring maintenance problem. Current LXD, Multipass, and unit tests still contain hardcoded buildd-base-v7 values, while the Ubuntu implementation derives its tag from Base.compatibility_tag, confirming the cleanup remains unresolved.
Evaluated by: mr-cal-bot
Impact:
38
Quick Win:
22
Complexity:
32
Confidence:
94
Actionability:
84
Issue body
### What needs to get done
Directly reference the compatibility tag from the tests, rather than hardcoding it.
See https://github.com/canonical/craft-providers/pull/382#discussion_r1297563019
### Why it needs to get done
When the compatibility tag needs to be bumped, it can be changed in 50 places in the test suite, but not all of them have to be changed. This is confusing and can be error prone.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
22
Complexity:
32
Confidence:
94
Actionability:
84
|
keep open | Tests still hardcode buildd-base-v7 while production derives it from Base.compatibility_tag, leaving compatibility-tag bumps vulnerable to inconsistent test updates. | |
| stealth/space-bunny-alpha |
Impact:
34
Quick Win:
25
Complexity:
20
Confidence:
97
Actionability:
91
|
keep open | Replace hardcoded compatibility tags in tests with references to the base classes. Some LXD integration tests still contain base-v7 literals, so the requested test cleanup remains unresolved. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
30
Quick Win:
22
Staleness:
75
Complexity:
25
Confidence:
65
Support Request:
10
|
close stale | Enhancement to avoid hardcoding compatibility tags in tests by referencing them from a single source. Open for 3 years with no maintainer comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
80
Complexity:
25
Confidence:
85
Support Request:
0
|
needs triage | Enhancement to refactor the test suite to dynamically reference a compatibility tag instead of hardcoding it in ~50 locations, reducing error-prone manual updates. Currently open with no maintainer comments or assignment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
70
Complexity:
20
Confidence:
75
Support Request:
0
|
needs triage | Enhancement to replace hardcoded compatibility tags in the test suite with dynamic references to prevent error-prone updates. Open for nearly three years with zero comments, awaiting maintainer triage. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/craft-providers#382
(confidence 99%)
The requested test change originated from the linked review discussion on PR #382.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #145 bases: allow overriding of compatibility tag | craft-providers | merged | Merged PR #145 added an optional compatibility_tag to BuilddBase, allowing overrides while preserving default behavior (CRAFT-1248). | |
| #50 bases: add compatibilty_tag requirement for Base (CRAFT-144) | craft-providers | merged | Merged PR #50, adding the compatibility_tag requirement for Base under CRAFT-144. | |
| #513 chore(bases): bump compatibility tag to v7 | craft-providers | merged | Merged as 37b0cf7: bumped Base.compatibility_tag from "base-v6" to "base-v7" across 7 base modules (41 lines), invalidating old instances because some image sources changed from `ubuntu` to `buildd`. |