Broken remote bug trackers should not cause OOPSes
Bug #719738 reported by
William Grant
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
William Grant | ||
Bug Description
checkwatches logs an OOPS for every ProtocolError. These are often caused by the remote bug tracker being offline or otherwise broken, and most require no action on our part. At least 503 and 504 can be sensibly excluded as remote issues, and make up the majority of such exceptions.
See for example OOPS-1872CCW1022.
Related branches
lp:~wgrant/launchpad/squash-cw-protocolerrors
- Tim Penhey (community): Approve
-
Diff: 225 lines (+85/-12)6 files modifiedlib/lp/bugs/doc/checkwatches-cli-switches.txt (+1/-0)
lib/lp/bugs/doc/checkwatches.txt (+3/-1)
lib/lp/bugs/scripts/checkwatches/core.py (+13/-5)
lib/lp/bugs/scripts/checkwatches/tests/test_core.py (+52/-6)
lib/lp/bugs/scripts/checkwatches/utilities.py (+8/-0)
lib/lp/testing/factory.py (+8/-0)
| tags: | added: bugwatch oops |
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 719738] [NEW] Broken remote bug trackers should not cause OOPSes | #1 |
Revision history for this message
| Gavin Panella (allenap) wrote | #2 |
| Changed in launchpad: | |
| assignee: | nobody → William Grant (wgrant) |
| status: | Triaged → In Progress |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #3 |
| Changed in launchpad: | |
| milestone: | none → 11.03 |
| tags: | added: qa-untestable |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Do such issues get reported elsewhere - e.g. against the tracker in the web UI?