← Back to issue list

Add a way to run a spread test on only certain architectures

View original Github issue

Metadata

Project
craft-application
Number
#1028
Type
issue
State
open
Author
lengau
Labels
Status: Triaged Type: Enhancement
Created
Updated
Closed
—

Current evaluation

Architecture-scoped Spread tasks are requested because test systems currently expose only distribution and version. The triaged enhancement remains open with a concrete different-architecture fixture and no identified resolving PR.

Suggested action: keep open

Reason: The Status: Triaged and Type: Enhancement labels indicate maintainer categorization, and the body identifies the missing capability with a concrete different-architecture task.yaml example. The requested filtering is clear, but the exact syntax, defaults, and behavior across all craft test systems still require design and implementation work; no commit referencing #1028 was found.

Evaluated by: mr-cal-bot

Impact: 46 Quick Win: 16 Complexity: 52 Confidence: 87 Actionability: 74

Issue body

### Bug Description Because all craft test systems end up just declaring the distribution and version, there's no way to set a task.yaml file to only run on a specific architecture. ### To Reproduce Consider this testcraft test: https://github.com/canonical/craft-application/blob/4a58068490abd7027a824c91851c2a2e7c76a58e/tests/spread/testcraft/different-architecture/task.yaml ### part yaml ```shell n/a ``` ### Relevant log output ```shell n/a ```

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 46
Quick Win: 16
Complexity: 52
Confidence: 87
Actionability: 74
keep open Architecture-scoped Spread tasks are requested because test systems currently expose only distribution and version. The triaged enhancement remains open with a concrete different-architecture fixture and no identified resolving PR.
qwen/qwen3.6-35b-a3b
Impact: 50
Quick Win: 18
Complexity: 50
Confidence: 70
Actionability: 70
keep open Enhancement to add architecture filtering to spread tests in task.yaml files. Currently craft test systems only declare distribution/version, not architecture.
qwen/qwen3.8-27b
Impact: 40
Quick Win: 22
Staleness: 50
Complexity: 45
Confidence: 75
Support Request: 5
keep open Enhancement to enable architecture-specific spread test filtering; arm64 system still commented out in spread.yaml. Triaged by maintainer, Jira ticket CRAFT-5055 created, no further activity in ~5.5 months.
qwen/qwen3.6-35b-a3b
Staleness: 45
Complexity: 30
Confidence: 85
Support Request: 10
keep open Enhancement to allow filtering spread tests by architecture in task.yaml. Currently triaged and awaiting implementation, with no recent activity or maintainer discussion beyond initial triage.
qwen3.6-35b-a3b-mtp-q6
Staleness: 70
Complexity: 30
Confidence: 80
Support Request: 0
keep open Enhancement request to allow filtering spread tests by architecture in task.yaml. Currently triaged but inactive for 114 days with no implementation plan or maintainer discussion.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/craft-application#1027 (confidence 90%)

    Commit 15f48281 changed the same different-architecture task.yaml fixture while adding support for building on other compatible architectures.

Related issues

No related issues found above the similarity threshold.