OOPS registering http branch
Bug #245209 reported by
Diogo Matsubara
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:
OOPS-914SMPU2
error-explanation: exceptions.
Changed in launchpad-bazaar: | |
assignee: | nobody → jml |
importance: | Undecided → High |
status: | New → In Progress |
To post a comment you must log in.
So a new test (test_stderrLog gedToOOPS) failed -- in PQM -- in a way which suggests that no oops got logged, or that an oops got logged but wasn't returned by getLastOopsRepo rt(). Don't know which, don't know how to tell. Doesn't seem to be reproducible locally.