fix: use self hosted runner for tics
Metadata
Current evaluation
Merged a CI fix switching to self-hosted runners. This resolves failing LXD-dependent tests by leveraging runners preconfigured for LXD. All CI checks passed prior to merge.
Suggested action: —
No scores available.
Issue body
At some point in time it looks like Charmcraft started to use lxd in tests, the self hosted runners are mostly preconfigured for this to work out of the box.
---
Working action https://github.com/canonical/charmcraft/actions/runs/14606116055/job/40976094707?pr=2258
Failing action https://github.com/canonical/charmcraft/actions/runs/14605447468/job/40973362344
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged a CI fix switching to self-hosted runners. This resolves failing LXD-dependent tests by leveraging runners preconfigured for LXD. All CI checks passed prior to merge. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a fix to switch CI to self-hosted runners, resolving LXD test failures in Charmcraft. Preconfigured runner environments now ensure stable test execution. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #431 test: use tics self-hosted runner | fetch-service | merged | Merged into the tiobe branch after syncing with main. The update configures tests to use a self-hosted runner. Approved by two reviewers with all CI checks passing. | |
| #991 ci: fix TICS workflow failing on integration tests | craft-providers | merged | Merged fix for TICS CI workflow failing on integration tests. The runner lacked LXD and Multipass. Added PYTEST_ADDOPTS to exclude lxd_instance and multipass_instance markers during coverage runs. Approved and merged after passing all CI checks. |