Update snapcraft test to stable in CI tests
Metadata
Current evaluation
CI spread tests still install snapcraft from latest/edge; maintainer wants the stable channel used in tests once craft-test is published there. Still open, unlabelled, no discussion.
Suggested action: needs triage
Reason: The change is still not made: .github/workflows/tests.yaml still runs `sudo snap install snapcraft --classic --channel=latest/edge` in the snap-test job, and spread.yaml relies on the `craft` (craft-test) backend added by merged PR #386/commit 323b0e1. The issue carries no labels, no assignee and no comments, and its stated precondition ('once craft-test is available there') is unverified from the repo, so a maintainer needs to confirm stable now ships craft-test before the one-line workflow edit can be made — hence needs_triage rather than keep_open.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
28
Quick Win:
11
Complexity:
20
Confidence:
74
Actionability:
50
|
needs triage | CI spread tests still install snapcraft from latest/edge; maintainer wants the stable channel used in tests once craft-test is published there. Still open, unlabelled, no discussion. | |
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
15
Complexity:
27
Confidence:
79
Actionability:
64
|
needs triage | Requests using Snapcraft's stable channel in fetch-service CI tests once craft-test is available there; still open, unlabelled, and without maintainer discussion. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
26
Staleness:
85
Complexity:
15
Confidence:
70
Support Request:
10
|
close stale | Request to use Snapcraft from the stable channel in CI tests. Unlabelled, no maintainer comments, 487 days old. Related work snapcraft-rocks#85 was merged addressing the same concern. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
fetch-service#386
(confidence 92%)
Merged PR (commit 323b0e1, 'tests: update testing to use craft-test') moved CI to `snapcraft test` with the craft backend, which is why the snapcraft channel now gates the test run.
-
Related To:
snapcraft#3619
(confidence 40%)
A closed, unmerged snapcraft PR exploring edge-channel config for action-build; same channel-vs-craft-test tension but from the Snapcraft side.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #982 Publish testcraft from PRs to relevant branches | craft-application | open | Enhancement (triaged, by maintainer) to add CI that publishes the testcraft snap from PRs to `latest/edge/craft-application-<pr#>` and main to `latest/edge/craft-application-main`, plus a PR comment with install commands. Explicitly blocked on canonical/craft-actions#48, which is still open; no such workflow exists in the repo yet. |