need logable output option or autodetected
Bug #1638514 reported by
Harald Sitter
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Fix Released
|
Medium
|
Sergio Schvezov | ||
Bug Description
We run snapcraft through Jenkins which has the potential of obsurdly blowing up the log thanks to progress and busy indicators.
The download progress when downloading a source is too fine-grained in a logging potential (albeit useful). Should maybe update only every 25% or so.
The busy indication during `snapcraft push` though is madness. Since it updates every second until the autoreview happened, which may be delayed because of a pending manual review, it can spam the log with thousands of needless lines with progress indicating characters. I am currently looking at a ~20MiB log file.
| summary: |
- need logable output option + need logable output option or autodetected |
| Changed in snapcraft: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| tags: | added: ui |
Revision history for this message
| Sergio Schvezov (sergiusens) wrote | #1 |
| Changed in snapcraft: | |
| status: | Confirmed → In Progress |
| assignee: | nobody → Sergio Schvezov (sergiusens) |
| milestone: | none → 2.23 |
Revision history for this message
| Sergio Schvezov (sergiusens) wrote | #2 |
| Changed in snapcraft: | |
| status: | In Progress → Fix Committed |
| Changed in snapcraft: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
we are supporting TERM=dumb now as well as isatty