Launchpad itself

Bugtask expiration cronjob not reporting OOPSes

Bug #765291 reported by j.c.sackett
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
j.c.sackett
Launchpad itself 11.05

Bug Description

The bugtask expiration cronjob was failing on a permission error, but not reporting OOPSes. We need to get the cronjob connected to the OOPS reports

Related branches

lp://staging/~jcsackett/launchpad/bug-expiration-doesnt-oops
Robert Collins (community): Approve
Diff: 27 lines (+10/-4)
1 file modified
cronscripts/expire-bugtasks.py (+10/-4)
Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 765291] [NEW] Bugtask expiration cronjob not reporting OOPSes

Hmm, i think this was a dupe; it failed to report the oops because of
a participation error IIRC.

Revision history for this message
j.c.sackett (jcsackett) wrote :

It's not a dupe, the specifics were reported in bug 760950, which is about the script failing.

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 765291] Re: Bugtask expiration cronjob not reporting OOPSes

On Tue, Apr 19, 2011 at 11:28 AM, j.c.sackett <email address hidden> wrote:
> It's not a dupe, the specifics were reported in bug 760950, which is
> about the script failing.

Ah cool. Thanks!

Revision history for this message
Launchpad QA Bot (lpqabot) wrote :

Fixed in stable r12888 (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/12888) by a commit, but not testable.

Changed in launchpad:
milestone: none → 11.05
tags: added: qa-untestable
Changed in launchpad:
status: In Progress → Fix Committed
Данило Шеган (danilo)
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.
Subscribing...

Other bug subscribers

Remote bug watches

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