Core22 unit tests in snapcraft fails with craft application 5.5.0
Metadata
Current evaluation
Closed as deferred with no direct fix; craft-application#812 remained identified as the source of the core22 validation regression in 5.5.0.
Resolution: closed stale
Reason: The issue was closed as deferred without a resolving Snapcraft commit or explanatory maintainer comment. craft-application#812 was identified as introducing the validation mismatch, but no direct Snapcraft fix was cited.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
Updating to craft-application 5.5.0 causes core22 unit tests to fail with:
```
Bad snapcraft.yaml content:
- 'platforms' key is not supported for base 'core22'. Use 'architectures' key instead.
```
([source](https://github.com/canonical/snapcraft/actions/runs/16371073855/job/46263753870?pr=5612#step:4:368))
This is due to [this line](https://github.com/canonical/craft-application/pull/812/files#diff-5a1e547ec3a0d86ebd396803eabf6624306b1a16cef192d4c55487897a9d8ea6R476) from https://github.com/canonical/craft-application/pull/812.
We don't yet know if snapcraft mis-using craft-application or if this is a craft-application regression.
### Why it needs to get done
So Snapcraft can get `craft test` fixes from craft-app 5.5.0.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed as deferred with no direct fix; craft-application#812 remained identified as the source of the core22 validation regression in 5.5.0. | |
| stealth/space-bunny-alpha | — | closed stale | Craft-application 5.5.0 broke Snapcraft core22 unit tests by rejecting the platforms key; the report was closed as deferred without a code fix. | |
| stealth/space-bunny-alpha | — | closed stale | Closed as deferred with no code fix cited. craft-application PR #812 was identified as the source of the core22 validation failure introduced in version 5.5.0. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and deferred. The core22 test failure was traced to a validation change in craft-application PR #812. The issue was logged internally as SNAPCRAFT-1188 for tracking. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. The craft-application 5.5.0 validation regression causing core22 unit test failures was resolved, allowing snapcraft to adopt upstream craft test fixes. Tracked as Jira SNAPCRAFT-1188. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution and deferred. The craft-application 5.5.0 regression breaking core22 tests was tracked via internal Jira ticket SNAPCRAFT-1188 for further investigation. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Upgrading to craft-application 5.5.0 broke core22 unit tests due to a platforms key validation error. The issue was closed and triaged, with an internal Jira ticket SNAPCRAFT-1188 created to track the fix. |
Update history
No update history recorded yet.
Related work
-
Caused By:
canonical/craft-application#812
(confidence 99%)
The issue identifies this pull request as the change that caused core22 snapcraft.yaml validation to fail in craft-application 5.5.0.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #6450 fix(test): error for core22 snaps | snapcraft | closed | PR #6450 proposed an early core22 error for snapcraft test, but was closed unmerged with review pending; #5479 remains open. | |
| #6336 Snapcraft 9: snapcraftctl errors in core22 snaps | snapcraft | closed | Fixed a validator bug preventing core22/core24 snaps without a `base` key from using `snapcraftctl`. Merged as #6499, resolving #6336. | |
| #300 Remote-build: use craft-application for core22 | craft-application | closed | Core22 remote builds moved to craft-application in merged Snapcraft PR #4724 (commit 9905f2831), removing the legacy core22 build path. |