Unable to use spread artifacts with `charmcraft test`
Metadata
Current evaluation
charmcraft test cannot pass -artifacts to spread; unlabelled, 0 comments, last activity 381 days ago, similar to #2105 (verbose flag). No maintainer triage.
Suggested action: needs triage
Reason: No labels, no comments, no maintainer response in 577 days. The issue is a real feature gap (spread -artifacts not exposed via charmcraft test), similar to #2105 which is also open. Needs triage to determine if this is in scope.
Impact:
30
Quick Win:
21.0
Staleness:
75
Complexity:
30
Confidence:
60
Support Request:
10
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 |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
21.0
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. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
25
Confidence:
85
Support Request:
10
|
needs triage | charmcraft test lacks support for the -artifacts flag when invoking spread, preventing artifact collection during testing. Open for over 300 days with no comments, it requires triage and implementation. |
Update history
No update history recorded yet.
Related work
-
Related To:
charmcraft#2105
(confidence 80%)
Same pattern: charmcraft test does not pass through spread flags (-verbose in #2105, -artifacts here).
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2105 Unable to enable spread verbose with `charmcraft test` | charmcraft | open | charmcraft test cannot forward -vv to spread for verbose CI output. Custom test command was removed in #2385 in favor of the upstream spread-based command, and PR #1988 proposing a --verbose flag was closed as superseded by that migration. |