← Back to team overview

launchpad-dev team mailing list archive

Re: deployments blocked: bug mail not happening

 

On Mon, Nov 1, 2010 at 10:04 AM, Robert Collins
<robert.collins@xxxxxxxxxxxxx> wrote:
> On Tue, Nov 2, 2010 at 2:40 AM, Deryck Hodge <deryck.hodge@xxxxxxxxxxxxx> wrote:
>> On Fri, Oct 29, 2010 at 7:00 PM, Robert Collins
>> <robert.collins@xxxxxxxxxxxxx> wrote:
>>> So I've marked rRevision 11794 as bad, but I haven't rolled it back [yet].
>>>
>>> We're not getting bug mail from launchpad on qastaging or staging,
>>> which is rather concerning; we've verified that sending mail on asuka
>>> gets to the staging mailbox.
>>
>> I think everything is working fine.  I poked at a bug on staging
>> (changed status, privacy, and commented) and then asked Tom to run
>> ./cronscripts/send-bug-notifications.py on staging, and then checked
>> the staging IMAP mail box.  I saw the mail I expected.  So I've marked
>> the bug as qa-ok and removed the bad commit tag.
>>
>> Was this a case of not running
>> ./cronscripts/send-bug-notifications.py?  It has to be run manually.
>>
>> Or perhaps this was something else that is now fixed and no one replied here?
>
> Not sure. We also need to check that structural subscribers were
> notified as well.
>

Yes, structural subscribers were notified as well.  I checked the mail
for various rationale's (direct subscriber, direct subscribing team,
structural) and also against the subscribers lists on the bug.

Cheers,
deryck


-- 
Deryck Hodge
https://launchpad.net/~deryck
http://www.devurandom.org/



Follow ups

References