ci: check charms generated by `charmcraft init`
Metadata
Current evaluation
Merged PR #2436 added dedicated Spread coverage to verify charms generated for Kubernetes and machine profiles pass linting and unit tests.
Resolution: closed resolved
Reason: canonical/charmcraft#2436 was approved and merged. It added a dedicated init-generated charm test beyond the existing full-lifecycle coverage.
Evaluated by: mr-cal-bot
No scores available.
Issue body
This PR adds a spread test that checks the charms produced by `charmcraft init --profile=kubernetes` and `charmcraft init --profile=machine`. We expect both charms to pass linting and unit tests.
This is actually already covered by one of the existing spread tests - [smoketests/full-lifecycle](https://github.com/canonical/charmcraft/blob/main/tests/spread/smoketests/full-lifecycle/task.yaml) - but in discussion with Alex we decided to add a dedicated test.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #2436 added dedicated Spread coverage to verify charms generated for Kubernetes and machine profiles pass linting and unit tests. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #2436 (commit 9d40ec2f), adding dedicated Spread tests that lint and run unit tests on charms generated by `charmcraft init` for Kubernetes and machine profiles. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged a dedicated CI spread test validating linting and unit tests for charms generated by charmcraft init across kubernetes and machine profiles. Approved by two reviewers, passes CI checks, and adds 25 lines of test configuration. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a dedicated CI spread test to verify linting and unit tests for charms generated by charmcraft init across kubernetes and machine profiles, supplementing existing coverage. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #328 charmcraft init produces error charm for machine charms | charmcraft | closed | Machine charms gained a dedicated charmcraft init profile, resolving Kubernetes-only initialization; the change was merged in PR #868 (commit 2ed9033c). | |
| #49 ci: test the charmcraft actions in more places | craft-actions | merged | Merged PR #49 in commit a8e5310, expanding Charmcraft action CI coverage across more Ubuntu architectures, channels, and pinned-revision runs. | |
| #2426 fix(test): fix the reactive charm spread test | charmcraft | merged | Merged in canonical/charmcraft#2426 via commit 7c33dd1b, applying a one-line fix to the reactive-charm spread test for CHARMCRAFT-641. | |
| #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. |