Some tests will require the charm plugin to be enabled
Metadata
Current evaluation
Open, unlabelled issue: charmcraft PR #2722 may make craft-application tests depend on the charm plugin; the maintainer asks to remove that dependency, but no affected test or fix is identified.
Suggested action: needs triage
Reason: The body explicitly links charmcraft PR #2722 as the change that would make some tests require the charm plugin, confirming a real test-infrastructure concern. However, the issue has no labels, comments, assignee, failing-test output, or named tests, and its only reproduction instruction is to run the tests, so maintainer triage is needed to determine the intended change.
Evaluated by: mr-cal-bot
Impact:
35
Quick Win:
13
Complexity:
35
Confidence:
80
Actionability:
55
Issue body
### Bug Description
With https://github.com/canonical/charmcraft/pull/2722/ we will need the charm plugin to be enabled. We need to undo this.
### To Reproduce
Run the tests.
### part yaml
```shell
```
### Relevant log output
```shell
n/a
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
13
Complexity:
35
Confidence:
80
Actionability:
55
|
needs triage | Open, unlabelled issue: charmcraft PR #2722 may make craft-application tests depend on the charm plugin; the maintainer asks to remove that dependency, but no affected test or fix is identified. | |
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
11
Complexity:
34
Confidence:
71
Actionability:
44
|
needs triage | Untriaged test coupling: charmcraft#2722 would make some craft-application tests require the external charm plugin, which must be removed. | |
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
21
Complexity:
30
Confidence:
85
Actionability:
66
|
needs triage | charmcraft#2722 would make some craft-application tests require the charm plugin; the maintainer asks to undo that dependency, but no failing test or follow-up is recorded. | |
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
16
Complexity:
28
Confidence:
88
Actionability:
56
|
needs triage | A maintainer says test changes associated with charmcraft#2722 made some tests require enabling the charm plugin and asks to undo this; no triage is recorded. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
50
Quick Win:
40
Staleness:
75
Complexity:
20
Confidence:
80
Support Request:
0
|
needs triage | Test configuration requires enabling the charm plugin following upstream charmcraft#2722; currently unlabelled and awaiting maintainer review. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
45
Complexity:
15
Confidence:
90
Support Request:
10
|
needs triage | Tests require the charm plugin to be enabled per PR #2722. Unlabelled, unassigned, and inactive with no maintainer comments. Requires triage to assess and prioritize. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
45
Complexity:
20
Confidence:
85
Support Request:
0
|
needs triage | Issue notes that tests require the charm plugin to be enabled following PR #2722, and states the need to revert this change. Currently unlabelled and awaiting maintainer review. |
Update history
No update history recorded yet.
Related work
-
Caused By:
charmcraft#2722
(confidence 100%)
The issue explicitly identifies this charmcraft PR as the change that would introduce the charm-plugin test dependency.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #243 Initial tests from `charmcraft init` do not pass | charmcraft | closed | Superseded by charmcraft#247, which took ownership of redesigning charmcraft init and its generated tests; no direct fixing implementation was recorded for #243. | |
| #160 Have a way for charmcraft to run the tests | charmcraft | closed | No dedicated test command was added; maintainers directed users to override-build in charmcraft.yaml, running craftctl build before tests such as pytest. | |
| #1851 How-to doc for charmcraft test | charmcraft | open | Documentation request from a maintainer to write a how-to guide for the undocumented `charmcraft test` command. Open with no labels, assignee, or maintainer triage; only an automated Jira-sync bot comment (CRAFT-3957). | |
| #1326 fix(test): fix reactive plugin test if 'charm' tool is installed | charmcraft | merged | Merged test-only fix making reactive plugin tests deterministic when the charm executable is installed, via PR #1326 and commit 4a573702. | |
| #1235 tests: re-enable reactive charms test | charmcraft | merged | Merged PR canonical/charmcraft#1235 as commit bff2a6a3, re-enabling the reactive charms test with a one-line change after two approvals. |