hard to debug librarian
Bug #631124 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Theres no obvious way, and in fact there may be no supported way at all at the moment to debug the librarian with tests.
Specifically, if there is a test case that provokes a librarian bad behaviour (such as a 500), its very hard/impossible to do that with pdb in the librarian so that you can debug what is happening.
| Changed in launchpad-foundations: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| Gary Poster (gary) wrote | #1 |
Revision history for this message
| Robert Collins (lifeless) wrote | #2 |
To post a comment you must log in.
I'd like to fix, but I don't know an answer. I've done very painful pdbs in the past when I had to debug Twisted bits. Is there a standard Twisted approach to this?