Soyuz scripts overuse DEBUG in logs
Bug #54348 reported by
Malcolm Cleaton
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Many scripts in Soyuz use DEBUG for almost all of their logging, including the logging it's currently vital for tests to check, or people running the script to read, to see what it's done at all.
Some DEBUG logging needs to be promoted to INFO, WARNING or, in some cases, even ERROR.
As a general aim, we shouldn't have to rely on DEBUG-level logging in functional tests to find out whether or not the script is doing what we want it to. It also wouldn't hurt us if, for example, scripts could be run with INFO on the console and DEBUG in a file, and we ensured the output made sense like that.
See also bug 117166
| Changed in soyuz: | |
| importance: | Untriaged → Low |
| status: | Unconfirmed → Confirmed |
| description: | updated |
Revision history for this message
| Celso Providelo (cprov) wrote | #1 |
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #2 |
| Changed in soyuz: | |
| milestone: | 1.1.12 → 1.2.3 |
| Changed in soyuz: | |
| milestone: | 1.2.3 → none |
To post a comment you must log in.
not 1.1.7