Investigate tox linting issues not being picked up in spread tests.
Metadata
Current evaluation
Closed with no recorded fix; tox lint failures were not wired into the full-lifecycle spread test.
Resolution: closed stale
Reason: Issue #1553 was closed without explanation or a resolving PR or commit. Its only comment was the automated creation of internal ticket CRAFT-2560, providing no evidence that the requested lint coverage was implemented.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
Ensure that linting issues from tox runs cause the `full-lifecycle` spread test to fail.
See: https://github.com/canonical/charmcraft/pull/1551/files#r1505197796
### Why it needs to get done
The templates should always generate code that pass linting and tests.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | Closed with no recorded fix; tox lint failures were not wired into the full-lifecycle spread test. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a linked fix after PR #1551 exposed the gap; no change was recorded to make tox lint failures fail the full-lifecycle spread test. | |
| stealth/space-bunny-alpha | — | closed stale | No resolving change was recorded; after Jira bot ticket CRAFT-2560 was created, the maintainer’s tox-lint coverage request was closed without an explanation or linked fix. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without a fix or linked PR. Likely abandoned or superseded. The request was to ensure tox linting failures trigger the full-lifecycle spread test. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
92
Complexity:
35
Confidence:
85
Support Request:
10
|
needs triage | Unlabelled issue requesting investigation into why tox linting failures are not caught by spread tests. Open for over two years with no maintainer response or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
35
Confidence:
85
Support Request:
5
|
close stale | Internal task to fix tox linting detection in spread tests. Open for over two years with no maintainer response or updates, making it stale and likely superseded by current CI workflows. |
Update history
| Date | Change |
|---|---|
| closed |
Related work
-
Related To:
canonical/charmcraft#1551
(confidence 98%)
The issue originates from a review finding in this PR, but #1551 was not recorded as resolving #1553.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1484 fix(spread): run tox in lifecycle spread test | charmcraft | merged | Merged #1484, which adds tox execution to the lifecycle spread test and fixes #1471. | |
| #215 test: add tox environments for snapping and running spread tests | rockcraft | closed | Approved but never merged; the tox convenience change was closed unmerged after prolonged inactivity, with README updates and four review comments unresolved. |