Use `snapcraft test` for spread tests
Metadata
Current evaluation
Dogfooding task to switch craft-application CI from running spread directly to using snapcraft test. Triaged; open PR #1038 stalled ~165 days with failing CI; workflow still runs spread directly at HEAD.
Suggested action: keep open
Reason: The issue is triaged (Status: Triaged label) and still applicable: at HEAD, .github/workflows/spread.yaml still runs `spread` directly rather than `snapcraft test`. Open PR #1038 directly implements it but has sat 165 days with 0 reviews and failing craft-test CI, and merged #1168 deprecated spread.yaml in favor of <app-name>-test.yaml, so the PR needs a refresh rather than closure.
Impact:
25
Quick Win:
13.75
Staleness:
55
Complexity:
45
Confidence:
80
Support Request:
0
Issue body
### What needs to get done
Instead of using spread directly, switch to using `snapcraft test`
### Why it needs to get done
Dogfooding
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
13.75
Staleness:
55
Complexity:
45
Confidence:
80
Support Request:
0
|
keep open | Dogfooding task to switch craft-application CI from running spread directly to using snapcraft test. Triaged; open PR #1038 stalled ~165 days with failing CI; workflow still runs spread directly at HEAD. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
65
Complexity:
15
Confidence:
85
Support Request:
0
|
keep open | Switch from direct spread usage to snapcraft test for dogfooding purposes. Triaged by maintainer, currently inactive with no recent technical discussion or implementation progress. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
55
Complexity:
30
Confidence:
75
Support Request:
0
|
keep open | Switching spread tests to use snapcraft test for dogfooding. The issue is triaged and has been inactive for over 111 days, with an internal Jira ticket referenced. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
75
Support Request:
5
|
close stale | Switch spread tests to use snapcraft test instead of direct spread execution to improve dogfooding. Currently triaged and awaiting assignment, with no recent activity in 89 days. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
craft-application#1038
(confidence 85%)
Open PR titled 'ci(spread): switch from manually running spread to using snapcraft test' directly implements this task, but is stalled 165 days with 0 reviews and failing CI on craft-test jobs.
-
Related To:
craft-application#1168
(confidence 80%)
Merged PR that added <app-name>-test.yaml parsing and deprecated spread.yaml; it is a prerequisite for the dogfooding switch and changed the target file of PR #1038.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1038 ci(spread): switch from manually running spread to using snapcraft test | craft-application | open | CI config change to run spread tests via `snapcraft test` instead of manually. 165 days old, 0 reviews, CI failing on all craft-test jobs. Target file spread.yaml since deprecated in favor of <app-name>-test.yaml (#1168). | |
| #1272 tests: initial setup for the snapcraft snap tests with spread | snapcraft | merged | Merged to master following single reviewer approval. Introduced initial spread test infrastructure for snapcraft across four files (+39 lines). Code coverage remained stable at 95.33%. | |
| #5069 Test with snapd on candidate or edge | snapcraft | open | Enhancement to add a weekly spread smoke test running snapcraft against snapd on candidate or edge channel to catch integration bugs earlier. Triaged and tracked in Jira (CRAFT-3488) but no implementation found in the repo; dormant for ~14 months. | |
| #5845 test(spread): test building base and snapd snaps | snapcraft | merged | Merged spread tests for building base and snapd snaps. Despite initial CI failures linked to snapcraft issue #5843, the changes were approved and integrated to maintain build compatibility with mainline snapcraft. | |
| #2793 tests: enable SNAPCRAFT_BUILD_INFO for spread | snapcraft | merged | Merged following approval and passing CI. Enabled SNAPCRAFT_BUILD_INFO for spread tests to cover manifest changes. Included a fix for the nil-basic spread test. Minimal diff across three files. | |
| #386 tests: update testing to use craft-test | fetch-service | merged | Merged. Replaced direct spread calls with snapcraft test in workflows and spread.yaml, requiring a core24 base update. Approved by two reviewers and modified 10 files (+56/-125 lines). | |
| #5389 test(spread): trace logs in spread tests | snapcraft | merged | Merged after approval. Added trace logging to spread tests. Despite CI failures from extra snapcraft output, the change was approved and merged following a related feature branch integration to prevent conflicts. | |
| #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. | |
| #4937 [DRAFT] publish test snap for spread tests | snapcraft | closed | Abandoned without merging. The draft debugging PR successfully published two revisions of the test-snapcraft-assertions snap to the staging store for spread testing, fulfilling its purpose. |