← Back to issue list

feat: add --verbose flag to pass -vv to spread from charmcraft test

View original Github issue

Metadata

Project
charmcraft
Number
#1988
Type
pull request
State
closed
Author
PietroPasotti
Labels
—
Created
Updated
Closed

Current evaluation

Closed unmerged as superseded by PR #2385 (commit b7730efc), which switched charmcraft test to the upstream test command.

Resolution: closed superseded

Reason: The maintainer closed the PR on 2025-08-05 because Charmcraft now uses the upstream test command. PR #2385, commit b7730efc, replaced the custom test implementation, making this proposed --verbose flag obsolete.

Evaluated by: mr-cal-bot

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
stealth/space-bunny-alpha — closed superseded Closed unmerged as superseded by PR #2385 (commit b7730efc), which switched charmcraft test to the upstream test command.
stealth/space-bunny-alpha — closed superseded PR #1988 was closed unmerged as redundant after PR #2385 (commit b7730efc) switched charmcraft test from the custom command to upstream test infrastructure.
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.

Update history

No update history recorded yet.

Related work

  • Superseded By: canonical/charmcraft#2385 (confidence 100%)

    Merged change replaced the custom test command targeted by PR #1988 with upstream test infrastructure.

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.
78%
#1660 feat: add test command and templates charmcraft merged Merged as commit 097a4e9a, adding `charmcraft test` with templates for local or remote Spread suites using a Multipass backend.
73%
#2385 feat!(test): switch from the custom test command to upstream charmcraft merged Merged PR charmcraft#2385 (commit b7730efc) for CHARMCRAFT-631, replacing charmcraft's custom 'test' command with craft-application's upstream test infrastructure; it fixes and closes issue #2364. Some spread tests on 20.04/22.04 still fail.
73%
#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.
73%
#1214 tests: add more charms to large spread tests charmcraft closed Closed unmerged after 1,135 days; its large-spread test expansion landed through merged PR canonical/charmcraft#1217 in commit 0f4591a9.
72%
#1514 feat(testing): add spread testing template files charmcraft closed Closed unmerged as superseded by #1660 (commit 097a4e9a), which added charmcraft test and Spread templates, plus merged follow-up #1686 (58d36668).
72%
#1555 refactor(tests/spread): stop use init in most spread tests charmcraft closed Closed unmerged and replaced by PR #1556, merged as commit 4682b32b, which updated Spread tests to use explicit charmcraft.yaml files instead of charmcraft init.
71%
#2672 fix: use `charmcraft pack` instead of `charmcraft pull` in different-dir-metadata spread test charmcraft closed Closed unmerged: the charmcraft pull -> pack fix for the different-dir-metadata spread test was superseded by PR #2694, merged as commit dd684338 using `charmcraft pack --verbose --project-dir=charm` plus output/restore checks.
70%
#136 charmcraft build needs a --verbose option charmcraft closed Closed as a duplicate of canonical/charmcraft#42, which was resolved by merged PR #137 (commit 56ce5431) to make global options, including verbosity, work consistently after subcommands.
70%