snapcraft hides error traces
Metadata
Current evaluation
Explained as configurable behavior: SNAPCRAFT_ENABLE_ERROR_REPORTING=0 or SNAPCRAFT_ENABLE_SILENT_REPORT=1 avoids prompting, while cat /tmp/*/trace.txt retrieves traces; reporter accepted the workaround.
Resolution: closed not a bug
Reason: ~jamesh documented two environment-variable settings in the 2018-09-03 comment, and ~saviq replied that reading /tmp/*/trace.txt was sufficient for CI. No merged fix or superseding change is shown.
Evaluated by: mr-cal-bot
No scores available.
Issue body
When snapcraft encounters an error, it displays this:
--
Sorry, Snapcraft ran into an error when trying to running through its
lifecycle that generated a trace that has been put in '/tmp/tmpoa2izsq_/trace.txt'.
You can anonymously report this issue to the snapcraft developers.
No other data than this traceback and the version of snapcraft in
use will be sent.
Would you like send this error data? (Yes/No/Always) [no]:
--
In CI, however, this is unhelpful, and waits indefinitely (I think travis does allocate a terminal, so checking for that alone might not be enough. A '--non-interactive' option or so could help.
Related wishlist bug: https://bugs.launchpad.net/snapcraft/+bug/1741900
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed not a bug | Explained as configurable behavior: SNAPCRAFT_ENABLE_ERROR_REPORTING=0 or SNAPCRAFT_ENABLE_SILENT_REPORT=1 avoids prompting, while cat /tmp/*/trace.txt retrieves traces; reporter accepted the workaround. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without a direct fix after environment-variable workarounds were identified; canonical/snapcraft#2259 later added trace output for non-TTY/CI runs. | |
| stealth/space-bunny-alpha | — | closed resolved | Snapcraft now prints error traces in non-TTY/CI output; PR #2259 merged as commit 6071cfb39, resolving LP #1790697. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The proposed non-interactive flag was never implemented, leaving CI error handling unchanged. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The report requested a non-interactive flag to prevent indefinite CI hangs during error reporting, but the issue was abandoned without implementation. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution, likely abandoned. Snapcraft's error trace prompt hangs in CI environments. A non-interactive flag was suggested to bypass anonymous reporting, but no fix was implemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Requested a non-interactive mode to prevent snapcraft from hiding error traces and blocking CI with indefinite prompts. Closed without resolution or implementation, likely abandoned due to prolonged inactivity. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1741900
(confidence 99%)
The issue body explicitly identifies #1741900 as a related wishlist bug.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1785231 enable error reporting by default | snapcraft (launchpad) | closed | Enabled Sentry error reporting by default in snapcore/snapcraft#2187 (commit f77a6c10a), with prompt-free reports controlled by SNAPCRAFT_ENABLE_SILENT_REPORTS. | |
| #1548492 Snapcraft swallows exceptions | snapcraft (launchpad) | closed | Added a global --debug flag for tracebacks and debug logs via merged PR ubuntu-core/snapcraft#332 (commit 580c43ebc). |