Use `rockcraft test` to test the rocks
Metadata
Current evaluation
Task to update spread.yaml and CI workflows in snapcraft-rocks to use `rockcraft test` for testing rocks. Open ~389 days with no labels, comments, or maintainer assessment; no evidence of implementation found.
Suggested action: needs triage
Reason: The issue has no labels, no comments, and no maintainer assessment in 389 days, showing no sign of triage, so needs_triage is the appropriate default. It is not a candidate for close_stale because there is no evidence the task is obsolete (repo inspection was unavailable, so I cannot confirm whether `rockcraft test` is already used in spread.yaml or the workflows). It is a CI/test-infrastructure task rather than a support request, with modest impact.
Impact:
25
Quick Win:
16.25
Staleness:
88
Complexity:
35
Confidence:
62
Support Request:
5
Issue body
Modify the `spread.yaml` file and the workflows so we're using `rockcraft test` to test the rocks.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
16.25
Staleness:
88
Complexity:
35
Confidence:
62
Support Request:
5
|
needs triage | Task to update spread.yaml and CI workflows in snapcraft-rocks to use `rockcraft test` for testing rocks. Open ~389 days with no labels, comments, or maintainer assessment; no evidence of implementation found. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
80
Support Request:
10
|
needs triage | Request to update spread.yaml and CI workflows to use rockcraft test for testing rocks. Open for 348 days with no comments, labels, or maintainer assessment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Request to update spread.yaml and CI workflows to use rockcraft test. Issue is unlabelled, inactive for over a year, and has zero comments. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
20
Confidence:
80
Support Request:
0
|
needs triage | Update spread.yaml and CI workflows to use rockcraft test for rock validation. Open 314 days with zero comments or labels. Awaiting triage and assignment to implement. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #618 Update snapstore page for rockcraft | rockcraft | open | Maintainer task to add source/docs/issue links and possibly a screenshot to the rockcraft Snap Store page. Core link request appears addressed via adopt-info + [project.urls] in pyproject.toml; no labels or maintainer response in 381 days. | |
| #389 Update snapcraft test to stable in CI tests | fetch-service | open | 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. | |
| #1093 feat(snap): add rockcraft.json to the snap | rockcraft | merged | Merged a pull request adding rockcraft.json to the snap. Requested by the Rocks team, this enables users to validate rockcraft.yaml against their installed version and check supported bases. Approved by two reviewers and passed CI checks. |