← Back to issue list

Some tests will require the charm plugin to be enabled

View original Github issue

Metadata

Project
craft-application
Number
#1092
Type
issue
State
open
Author
lengau
Labels
Created
Updated
Closed

Current evaluation

Test configuration requires enabling the charm plugin following upstream charmcraft#2722; currently unlabelled and awaiting maintainer review.

Suggested action: needs triage

Reason: The issue has been open for 81 days with zero comments, labels, or assignee. It references an upstream PR (charmcraft#2722) as the trigger for a test configuration change but lacks specific details on what exactly needs to be 'undone' or how to reproduce the failure, requiring maintainer assessment.

Impact: 50 Quick Win: 40.0 Staleness: 75 Complexity: 20 Confidence: 80 Support Request: 0

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
qwen3.6-35b-a3b-mtp-q6
Impact: 50
Quick Win: 40.0
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 20
Complexity: 15
Confidence: 85
Support Request: 5
needs triage Tests require the charm plugin to be enabled following PR #2722, with a request to revert the change. Currently unlabelled and awaiting triage.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: canonical/charmcraft#2722 (confidence 90%)

    Issue explicitly cites this PR as the reason the charm plugin must be enabled for tests to pass.

Related issues

Issue Project State Summary Similarity
#1198 tests: add charm library multiple versions update test charmcraft merged Merged after approval, adding a test for updating charm library multiple versions. The change introduces 120 lines to address CRAFT-1916 and issue #1020, with zero unresolved review comments.
70%