OOPS registering http branch

Bug #245209 reported by Diogo Matsubara
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Jonathan Lange

Bug Description

Since the rollout we have seen some OOPS while registering new http branches:

OOPS-913SMPM12, OOPS-913SMPM314

error-explanation: A process has ended with a probable error condition: process ended with exit code 1.

Jono has fix for this on bzr+ssh://devpad.canonical.com/code/jml/launchpad/bzr-http-mirroring which also fixes an IndexError oops and improve handling of bare Exception

OOPS-914SMPU2

error-explanation: exceptions.IndexError: list index out of range

Tags: lp-code oops
Changed in launchpad-bazaar:
assignee: nobody → jml
importance: Undecided → High
status: New → In Progress
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

So a new test (test_stderrLoggedToOOPS) failed -- in PQM -- in a way which suggests that no oops got logged, or that an oops got logged but wasn't returned by getLastOopsReport(). Don't know which, don't know how to tell. Doesn't seem to be reproducible locally.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

And this is the error on PQM: https://pastebin.canonical.com/7009/

Revision history for this message
Jonathan Lange (jml) wrote :

This has landed.

Changed in launchpad-bazaar:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.