lxd test_init should not run by default since it requires sudo
Metadata
Current evaluation
Closed as a duplicate of #222; sudo-requiring LXD tests are now gated behind a `with_sudo` pytest marker via merged PR #328 (commit 0a90009), so test_init no longer runs by default.
Resolution: closed superseded
Reason: Maintainer lengau closed the issue noting it is a dupe of #222. That duplicate was addressed by merged PR #328 (commit 0a90009), which added a `with_sudo` marker and parametrizes test_init/test_wait_ready into no-sudo and with-sudo variants.
Evaluated by: mr-cal-bot
No scores available.
Issue body
tests/integration/lxd/test_lxd.py::test_init
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Closed as a duplicate of #222; sudo-requiring LXD tests are now gated behind a `with_sudo` pytest marker via merged PR #328 (commit 0a90009), so test_init no longer runs by default. | |
| qwen/qwen3.6-35b-a3b | — | closed superseded | Duplicate of #222; test_init requires sudo and should be skipped in non-CI environments. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Duplicate Of:
canonical/craft-providers#222
(confidence 98%)
Maintainer explicitly said 'this is a dupe of #222' in the closing comment.
-
Likely Fixed By:
canonical/craft-providers#328
(confidence 90%)
Merged PR adding the sudo marker that resolves #222, which also covers test_init requested here.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #222 lxd integration tests run`sudo lxd init` | craft-providers | closed | LXD integration tests requiring sudo were marked and skipped by default, preventing routine runs of `sudo lxd init`; resolved by merged PR #328. |