`test` command fails to allocate LXD VMs when verbosity is `verbose` or `debug`
Metadata
Current evaluation
Triaged bug: snapcraft test allocates LXD VMs at default verbosity but fails at verbose or debug, with spread receiving no ADDRESS output; no resolving change is evidenced.
Suggested action: keep open
Reason: The issue is labeled Status: Triaged and Type: Bug, and provides a concrete passing/failing command pair plus the spread error that the craft backend returned an empty ADDRESS value. The inspected allocation path still constructs ADDRESS from ./spread/.extension, whose address comes from lxc ls, so a verbosity/output-routing regression test and fix remain justified; no resolving commit or PR is shown.
Evaluated by: mr-cal-bot
Impact:
45
Quick Win:
22
Complexity:
42
Confidence:
88
Actionability:
86
Issue body
### Bug Description
When using the `test` command, if verbosity is set to `verbose` or `debug`, LXD VMs will fail to allocate.
### To Reproduce
```
git clone https://github.com/lengau/astral-ty.git
snapcraft test # Works
snapcraft --verbosity=debug test # Fails to allocate the machine.
```
### Relevant log output
```shell
Creating snap package...
Packed astral-ty_0.0.23-8-gbc9e8a8_amd64.snap
Testing platform 'amd64'
Running spread tests
:: 2026-03-17 18:31:55 Project content is packed for delivery (35.93MB).
:: 2026-03-17 18:31:55 If killed, discard servers with: spread -reuse-pid=362911 -discard
:: 2026-03-17 18:31:55 Allocating craft:ubuntu-24.04...
:: 2026-03-17 18:31:58 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:32:10 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:32:25 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:32:40 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:32:55 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:33:10 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:33:25 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:33:40 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:33:55 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
22
Complexity:
42
Confidence:
88
Actionability:
86
|
keep open | Triaged bug: snapcraft test allocates LXD VMs at default verbosity but fails at verbose or debug, with spread receiving no ADDRESS output; no resolving change is evidenced. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
15
Complexity:
30
Confidence:
70
Actionability:
70
|
keep open | test command fails to allocate LXD VMs when verbosity is verbose or debug due to stdout interference with spread backend ADDRESS parsing | |
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
30
Staleness:
55
Complexity:
40
Confidence:
60
Support Request:
0
|
keep open | test command fails to allocate LXD VMs when verbosity is verbose or debug; spread backend allocate command returns empty ADDRESS. Triaged, no fix yet. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
65
Complexity:
35
Confidence:
90
Support Request:
5
|
keep open | snapcraft test fails to allocate LXD VMs when verbosity is set to verbose or debug, causing repeated allocation errors. Triaged bug with no maintainer response or fix in 126 days. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
35
Confidence:
85
Support Request:
5
|
keep open | snapcraft test fails to allocate LXD VMs when verbosity is verbose or debug. The bug is triaged and reproducible but has been inactive for 112 days with no assigned fix. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.