prefixing snapcraft with "time" makes it ignore --verbose
Metadata
Current evaluation
An unlabelled report says prefixing a core22 Snapcraft build with time leaves only a spinner and suppresses verbose output; no triage or confirmed resolution is recorded.
Suggested action: needs triage
Reason: The report provides an exact failing command, a working comparison without time, and LXD/Jammy/core22 context, making it suitable for reproduction. However, it has no labels, maintainer response, confirming investigation, or demonstrated reproduction against the current architecture, so the underlying emitter/progress behavior needs triage.
Evaluated by: mr-cal-bot
Impact:
34
Quick Win:
14
Complexity:
41
Confidence:
88
Actionability:
72
Issue body
running:
$ time snapcraft --destructive-mode --verbose
to measure build time of a snap gets me the regular spinner but no other output ...
removing the time command from the line makes it behave as expected (this is inside an lxd container running jammy and building with "base: core22")
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
34
Quick Win:
14
Complexity:
41
Confidence:
88
Actionability:
72
|
needs triage | An unlabelled report says prefixing a core22 Snapcraft build with time leaves only a spinner and suppresses verbose output; no triage or confirmed resolution is recorded. | |
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
9
Complexity:
58
Confidence:
78
Actionability:
64
|
needs triage | Snapcraft reportedly shows only a spinner and suppresses verbose output when wrapped with time; the exact core22 LXD/Jammy case remains open, untriaged, and lacks version diagnostics. | |
| stealth/space-bunny-alpha |
Impact:
22
Quick Win:
8
Complexity:
35
Confidence:
84
Actionability:
55
|
needs triage | Snapcraft produces only a spinner when run under `time`, despite --verbose. Reported for a core22 destructive-mode build in an LXD Jammy container; unresolved and untriaged. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
20
Quick Win:
14
Staleness:
95
Complexity:
30
Confidence:
50
Support Request:
40
|
close stale | Running `time snapcraft --verbose` suppresses verbose output, unlike running `snapcraft --verbose` directly. Reported 1465 days ago with no maintainer engagement or labels. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | Running snapcraft with the time command suppresses verbose output. Unlabeled, no maintainer interaction, inactive for nearly four years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
80
Support Request:
10
|
close stale | Running snapcraft with the time command suppresses verbose output. Unaddressed for over four years with no maintainer interaction or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
10
|
close stale | Running time snapcraft --verbose suppresses verbose output and shows only a spinner. Issue is over 3 years old with no maintainer response or activity. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1980686 snapcraft build won't allow `verbose` flag | snapcraft (launchpad) | closed | Snapcraft 7.0.11 fixed core22 only; canonical/snapcraft#4024 (be005b98d) later forwarded -v and --verbose to snapcraft_legacy for core18/core20 builds. |