`test` command fails to allocate LXD VMs when verbosity is `verbose` or `debug`
Metadata
Current evaluation
test command fails to allocate LXD VMs when verbosity is verbose or debug; spread backend allocate command returns empty ADDRESS. Triaged, no fix yet.
Suggested action: keep open
Reason: The issue is triaged (label: Status: Triaged, Type: Bug) with a clear reproduction and root cause visible in the code: emit.open_stream captures stdout, and at higher verbosity levels the emitter writes to stdout, corrupting the ADDRESS=$(...) command substitution in the spread backend allocate script. No fix commit found in testing.py history addressing this specific verbosity interaction.
Impact:
50
Quick Win:
30.0
Staleness:
55
Complexity:
40
Confidence:
60
Support Request:
0
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 |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
30.0
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. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
55
Complexity:
30
Confidence:
85
Support Request:
10
|
keep open | snapcraft test fails to allocate LXD VMs when verbosity is verbose or debug. Debug output pollutes stdout, breaking the backend's SSH address parsing. The bug is triaged and remains open with no recent activity. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.