Unable to use spread artifacts with `charmcraft test`
Metadata
Current evaluation
Request to pass spread's -artifacts flag through charmcraft test; TestCommand currently only exposes test expressions. No labels, comments, or maintainer response.
Suggested action: needs triage
Reason: Issue has no labels, comments, or maintainer response after 609 days, so it has not been triaged. Code inspection confirms charmcraft uses craft-application's TestCommand, whose _fill_parser only adds test_expressions and does not expose spread flags like -artifacts, making this a plausible upstream feature request rather than a charmcraft-specific bug.
Evaluated by: mr-cal-bot
Impact:
30
Quick Win:
5
Complexity:
55
Confidence:
60
Actionability:
40
Issue body
### Bug Description
#### Expected behavior
When running `charmcraft test`, it is possible to pass `-artifacts` to spread
#### Actual behavior
It is not possible to pass `-artifacts` to spread when using `charmcraft test`
Similar to #2105
### To Reproduce
N/A
### Environment
N/A
### charmcraft.yaml
```yaml
N/A
```
### Relevant log output
```shell
N/A
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| ~deepseek/deepseek-pro-latest |
Impact:
30
Quick Win:
5
Complexity:
55
Confidence:
60
Actionability:
40
|
needs triage | Request to pass spread's -artifacts flag through charmcraft test; TestCommand currently only exposes test expressions. No labels, comments, or maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
13
Complexity:
30
Confidence:
60
Actionability:
60
|
needs triage | charmcraft test cannot forward -artifacts flag to spread for artifact handling. Similar to #2105 for verbose flag. Open, unlabelled, no maintainer response. | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
21
Staleness:
75
Complexity:
30
Confidence:
60
Support Request:
10
|
needs triage | charmcraft test cannot pass -artifacts to spread; unlabelled, 0 comments, last activity 381 days ago, similar to #2105 (verbose flag). No maintainer triage. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
92
Complexity:
20
Confidence:
75
Support Request:
10
|
close stale | charmcraft test lacks support for passing the -artifacts flag to spread tests. Open for 536 days with zero maintainer engagement, labels, or reproduction steps. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
20
Confidence:
70
Support Request:
10
|
close stale | Unimplemented -artifacts flag passthrough to spread in charmcraft test. Inactive for over 17 months with zero maintainer comments, indicating it is no longer actionable or relevant to the current codebase. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
60
Support Request:
10
|
needs triage | Untriaged report requesting the ability to pass the -artifacts flag to spread during charmcraft test execution. Lacks reproduction steps, environment details, and maintainer interaction after 17 months. |
Update history
No update history recorded yet.
Related work
-
Related To:
charmcraft#2105
(confidence 90%)
Same reporter and same root cause: inability to pass spread flags (-vv there, -artifacts here) through charmcraft test.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2105 Unable to enable spread verbose with `charmcraft test` | charmcraft | open | Request to pass spread's -vv flag through `charmcraft test`; current TestCommand only accepts test expressions and has no maintainer triage yet. | |
| #1556 refactor(tests/spread): test with explicit charmcraft.yaml files | charmcraft | merged | Merged PR #1556 in commit 4682b32b, replacing prepare-step manipulation of charmcraft.yaml with explicit spread-test configuration files. | |
| #2482 `charmcraft test` v4.0.1 lost `--list` support | charmcraft | open | charmcraft test --list regressed in 4.0 after PR #2385 replaced the custom Spread wrapper; v4.0.1 rejects the flag. The issue is reproducible but remains unlabeled and untriaged. |