No indication when a job resulted in a user error

Bug #850974 reported by Aaron Bentley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Martin Pool

Bug Description

Log entries sometimes indicate that the job was incomplete, but there is no oops. Inspection of the code suggests that it could have been due to a user_error being raised. It should be clear when this is the case, and what error was raised. It may also be due to suprocess-side log messages not propagating through Twisted.

2011-09-15 11:57:42 DEBUG Running <UPDATE_PREVIEW_DIFF job for merge 75529 on ~jelmer/launchpad/pycurl-http-probing>, lease expires 2011-09-15 12:07:42.533877+00:00
2011-09-15 11:57:42 DEBUG Incomplete <UPDATE_PREVIEW_DIFF job for merge 75529 on ~jelmer/launchpad/pycurl-http-probing>

Related branches

Aaron Bentley (abentley)
summary: - No indication when a job resulted in a user error or retry
+ No indication when a job resulted in a user error
Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
Aaron Bentley (abentley)
Changed in launchpad:
assignee: nobody → Aaron Bentley (abentley)
status: Triaged → In Progress
Martin Pool (mbp)
Changed in launchpad:
assignee: Aaron Bentley (abentley) → Martin Pool (mbp)
Martin Pool (mbp)
tags: added: qa-untestable
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-untestable
Changed in launchpad:
status: In Progress → Fix Committed
Martin Pool (mbp)
tags: added: qa-untestable
removed: qa-needstesting
Changed in launchpad:
status: Fix Committed → 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.