checkwatches logs don't give enough information on error
Bug #210239 reported by
Graham Binns
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Undecided
|
Graham Binns | ||
Bug Description
The implementation of OOPS reporting for the checkwatches cronscript has led to the logs for checkwatches not including enough information when an error occurs. The error details are in the OOPS report, which is okay, but it's annoying to have to switch between the logs and the OOPS report when you're trying to debug a failure in the logs. A typical error message reads thus:
> An exception was raised when updating http://
Obviously this is pretty unhelpful. The log should at least include the error message, if any, the OOPS ID and perhaps a link to the error traceback (this is what used to happen pre-OOPS reporting).
| Changed in malone: | |
| status: | New → In Progress |
Revision history for this message
| Graham Binns (gmb) wrote | #1 |
Revision history for this message
| Graham Binns (gmb) wrote | #2 |
| Changed in malone: | |
| status: | In Progress → Fix Committed |
| Changed in malone: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
It's simpler to just include the OOPS id in the error message rather than a link to the traceback. Including both is an unnecessary duplication of effort, since OOPS reports contain tracebacks anyway.