warnings in the puller worker should lead to tracebacks
Bug #246114 reported by
Michael Hudson-Doyle
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
A warning printed to stderr is going to fail the job anyway and a traceback is a lot more useful.
| Changed in launchpad-bazaar: | |
| importance: | Undecided → Medium |
| Changed in launchpad-bazaar: | |
| status: | New → Triaged |
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in launchpad: | |
| importance: | Medium → Low |
To post a comment you must log in.
You can run it as "python -Werror command" which will translate all warnings into exceptions, which should give you nice tracebacks rather than short warnings and a future failure.
At least, if they are using warnings.warn() it is possible they are using a different technique to write to stderr.