snapcraft hides error traces
Metadata
Current evaluation
Abandoned. The proposed non-interactive flag was never implemented, leaving CI error handling unchanged.
Suggested action: —
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 |
|---|---|---|---|---|
| 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
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1477639 snapcraft has many exit points | snapcraft (launchpad) | closed | Abandoned. The suggestion to centralize error handling via exceptions instead of scattered sys.exit() calls was not adopted, leaving the codebase unchanged. | |
| #1548492 Snapcraft swallows exceptions | snapcraft (launchpad) | closed | Closed without implementation. The request for a --debug flag to expose exception backtraces was abandoned due to inactivity. |