Unable to enable spread verbose with `charmcraft test`
Metadata
Current evaluation
Request to pass spread's -vv flag through `charmcraft test`; current TestCommand only accepts test expressions and has no maintainer triage yet.
Suggested action: needs triage
Reason: The issue has no labels, comments, or maintainer response. Code inspection of craft-application's TestCommand and TestingService shows only test_expressions, shell, shell_after, and debug are exposed to spread, with no -vv/verbose passthrough, so the request remains valid but unassessed.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| ~deepseek/deepseek-pro-latest |
Impact:
35
Quick Win:
16
Complexity:
40
Confidence:
70
Actionability:
75
|
needs triage | Request to pass spread's -vv flag through `charmcraft test`; current TestCommand only accepts test expressions and has no maintainer triage yet. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
17
Complexity:
30
Confidence:
70
Actionability:
80
|
needs triage | Unable to pass -vv flag to spread when running charmcraft test. Issue is open with no labels or maintainer response after 603 days. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
28
Staleness:
70
Complexity:
30
Confidence:
75
Support Request:
10
|
needs triage | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
10
|
needs triage | Bug report: Unable to pass verbose flags to spread via charmcraft test. Issue is unlabelled, has no maintainer response, and has been inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
30
Confidence:
75
Support Request:
15
|
needs triage | User reports inability to pass verbose flag to spread via charmcraft test. Unlabeled, no maintainer comments, inactive for over ten months. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
25
Confidence:
75
Support Request:
15
|
needs triage | charmcraft test does not forward the -vv flag to spread for verbose output. The report includes expected vs actual behavior and reproduction attempts but remains unlabelled and unassessed by maintainers after over 14 months. |
Update history
No update history recorded yet.
Related work
-
Related To:
charmcraft#1988
(confidence 80%)
PR attempted to add a --verbose flag for spread -vv but was closed unmerged as redundant after the test command moved to upstream craft-application infrastructure.
-
Related To:
charmcraft#2130
(confidence 80%)
Similar request to pass spread's -artifacts flag through charmcraft test, also unlabelled and without maintainer response.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2130 Unable to use spread artifacts with `charmcraft test` | charmcraft | open | Request to pass spread's -artifacts flag through charmcraft test; TestCommand currently only exposes test expressions. No labels, comments, or maintainer response. | |
| #1988 feat: add --verbose flag to pass -vv to spread from charmcraft test | charmcraft | closed | Closed unmerged as superseded by PR #2385 (commit b7730efc), which switched charmcraft test to the upstream test command. | |
| #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. | |
| #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. |