feat: add --verbose flag to pass -vv to spread from charmcraft test
Metadata
Current evaluation
Superseded by migration to the upstream test command. The proposed --verbose flag was closed without review or merge after maintainers determined the upstream solution better addresses CI verbosity requirements.
Suggested action: —
No scores available.
Issue body
It is useful in CI to see the full verbose output from spread commands.
This PR adds an optional flag to the `charmcraft test` command.
`charmcraft test --verbose foo:bar/baz/qux:var` --> `spread -vv foo:bar/baz/qux:var`
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Superseded by migration to the upstream test command. The proposed --verbose flag was closed without review or merge after maintainers determined the upstream solution better addresses CI verbosity requirements. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without merging. The --verbose flag for passing -vv to spread was abandoned after the project adopted the upstream test command, making the custom implementation unnecessary. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The --verbose flag addition for charmcraft test was closed without merging. The change was abandoned after maintainers opted to adopt the upstream test command instead. |
Update history
No update history recorded yet.
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. | |
| #2021 feat(reactive): run charm build in verbose mode | charmcraft | merged | Merged after two approvals and passing CI. Automatically adds the --verbose flag to charm build arguments when no log level is specified, ensuring verbose output is captured in logs. Resolves issue #924. |