From victor.stinner at gmail.com  Tue May  9 11:01:27 2017
From: victor.stinner at gmail.com (Victor Stinner)
Date: Tue, 9 May 2017 17:01:27 +0200
Subject: [Python-buildbots] Email notifications on buildbot failures
Message-ID: <CAMpsgwaZ28GcR5_f1KAvcxWJ40yrVQ-o7iLDOSjQaT-L_deMTQ@mail.gmail.com>

Hi,

I would like to get an email notification each time the state of a
buildbot changed from green (success) to red (failed).

Maybe we can start with the master branch, but my long term plan is to
watch all branches (especially 2.7, 3.5, 3.6 and master), but maybe
exclude the special custom buildbots.

Can I use this list, or do you prefer that I create a different list?
If you prefer a different list, which name do you suggest?

I'm already watching "daily" (almost) buildbot waterfalls, but the UI
is not efficient, I have to scroll, ignore known broken buildbots,
ignore offline builders, etc. My request is to only get a notification
for the green => red state change, not any state change for now, that
would avoid spaming the list.

I always would like to use a mailing list to coordonate efforts to fix
buildbot issues.

Victor

From greg at krypto.org  Tue May  9 11:43:29 2017
From: greg at krypto.org (Gregory P. Smith)
Date: Tue, 09 May 2017 15:43:29 +0000
Subject: [Python-buildbots] Email notifications on buildbot failures
In-Reply-To: <CAMpsgwaZ28GcR5_f1KAvcxWJ40yrVQ-o7iLDOSjQaT-L_deMTQ@mail.gmail.com>
References: <CAMpsgwaZ28GcR5_f1KAvcxWJ40yrVQ-o7iLDOSjQaT-L_deMTQ@mail.gmail.com>
Message-ID: <CAGE7PNKxX1HtzHRLWR-RzSU8uXdxpX+vDzPT_-ZWjNedWsFtUw@mail.gmail.com>

Please do not send automated buildbot state transition mail to _this_
list.  Leave this low traffic list to communication from humans about
buildbots and infrastructure (the purpose as I understand it).

-gps

On Tue, May 9, 2017 at 8:01 AM Victor Stinner <victor.stinner at gmail.com>
wrote:

> Hi,
>
> I would like to get an email notification each time the state of a
> buildbot changed from green (success) to red (failed).
>
> Maybe we can start with the master branch, but my long term plan is to
> watch all branches (especially 2.7, 3.5, 3.6 and master), but maybe
> exclude the special custom buildbots.
>
> Can I use this list, or do you prefer that I create a different list?
> If you prefer a different list, which name do you suggest?
>
> I'm already watching "daily" (almost) buildbot waterfalls, but the UI
> is not efficient, I have to scroll, ignore known broken buildbots,
> ignore offline builders, etc. My request is to only get a notification
> for the green => red state change, not any state change for now, that
> would avoid spaming the list.
>
> I always would like to use a mailing list to coordonate efforts to fix
> buildbot issues.
>
> Victor
> _______________________________________________
> Python-Buildbots mailing list
> Python-Buildbots at python.org
> https://mail.python.org/mailman/listinfo/python-buildbots
>

From rosuav at gmail.com  Tue May  9 12:04:28 2017
From: rosuav at gmail.com (Chris Angelico)
Date: Wed, 10 May 2017 02:04:28 +1000
Subject: [Python-buildbots] Email notifications on buildbot failures
In-Reply-To: <CAGE7PNKxX1HtzHRLWR-RzSU8uXdxpX+vDzPT_-ZWjNedWsFtUw@mail.gmail.com>
References: <CAMpsgwaZ28GcR5_f1KAvcxWJ40yrVQ-o7iLDOSjQaT-L_deMTQ@mail.gmail.com>
 <CAGE7PNKxX1HtzHRLWR-RzSU8uXdxpX+vDzPT_-ZWjNedWsFtUw@mail.gmail.com>
Message-ID: <CAPTjJmqTHsn0se=uh7AVUFuFGKZCr0GyG58pSwTpd1VCqOxnxw@mail.gmail.com>

On Wed, May 10, 2017 at 1:43 AM, Gregory P. Smith <greg at krypto.org> wrote:
> Please do not send automated buildbot state transition mail to _this_
> list.  Leave this low traffic list to communication from humans about
> buildbots and infrastructure (the purpose as I understand it).

Agreed. Maybe a new list "buildbot-status at python.org"?

ChrisA

From victor.stinner at gmail.com  Tue May  9 12:08:23 2017
From: victor.stinner at gmail.com (Victor Stinner)
Date: Tue, 9 May 2017 18:08:23 +0200
Subject: [Python-buildbots] Email notifications on buildbot failures
In-Reply-To: <CAPTjJmqTHsn0se=uh7AVUFuFGKZCr0GyG58pSwTpd1VCqOxnxw@mail.gmail.com>
References: <CAMpsgwaZ28GcR5_f1KAvcxWJ40yrVQ-o7iLDOSjQaT-L_deMTQ@mail.gmail.com>
 <CAGE7PNKxX1HtzHRLWR-RzSU8uXdxpX+vDzPT_-ZWjNedWsFtUw@mail.gmail.com>
 <CAPTjJmqTHsn0se=uh7AVUFuFGKZCr0GyG58pSwTpd1VCqOxnxw@mail.gmail.com>
Message-ID: <CAMpsgwYorsboFFHSUc-V6M+HvACKtz-r2MqBHerbU7OVFK-9wQ@mail.gmail.com>

2017-05-09 18:04 GMT+02:00 Chris Angelico <rosuav at gmail.com>:
> Agreed. Maybe a new list "buildbot-status at python.org"?

Ok. I like this name.

Victor

From zachary.ware+pydev at gmail.com  Tue May  9 12:11:32 2017
From: zachary.ware+pydev at gmail.com (Zachary Ware)
Date: Tue, 9 May 2017 11:11:32 -0500
Subject: [Python-buildbots] Email notifications on buildbot failures
In-Reply-To: <CAPTjJmqTHsn0se=uh7AVUFuFGKZCr0GyG58pSwTpd1VCqOxnxw@mail.gmail.com>
References: <CAMpsgwaZ28GcR5_f1KAvcxWJ40yrVQ-o7iLDOSjQaT-L_deMTQ@mail.gmail.com>
 <CAGE7PNKxX1HtzHRLWR-RzSU8uXdxpX+vDzPT_-ZWjNedWsFtUw@mail.gmail.com>
 <CAPTjJmqTHsn0se=uh7AVUFuFGKZCr0GyG58pSwTpd1VCqOxnxw@mail.gmail.com>
Message-ID: <CAKJDb-OvmN6yPg3JB5sBV-C72tQ5yh10eQs_Vq70OV0ewn4Xfw@mail.gmail.com>

On Tue, May 9, 2017 at 11:04 AM, Chris Angelico <rosuav at gmail.com> wrote:
> On Wed, May 10, 2017 at 1:43 AM, Gregory P. Smith <greg at krypto.org> wrote:
>> Please do not send automated buildbot state transition mail to _this_
>> list.  Leave this low traffic list to communication from humans about
>> buildbots and infrastructure (the purpose as I understand it).

That is indeed the intended purpose :)

> Agreed. Maybe a new list "buildbot-status at python.org"?

I'd agree with this, or with using python-checkins at .  Dusty, commented
code in the master config looks like notifications used to go there,
but it was before my time and I don't know why it was stopped (if
indeed it ever happened).

-- 
Zach

From victor.stinner at gmail.com  Tue May  9 18:09:23 2017
From: victor.stinner at gmail.com (Victor Stinner)
Date: Wed, 10 May 2017 00:09:23 +0200
Subject: [Python-buildbots] Email notifications on buildbot failures
In-Reply-To: <CAKJDb-OvmN6yPg3JB5sBV-C72tQ5yh10eQs_Vq70OV0ewn4Xfw@mail.gmail.com>
References: <CAMpsgwaZ28GcR5_f1KAvcxWJ40yrVQ-o7iLDOSjQaT-L_deMTQ@mail.gmail.com>
 <CAGE7PNKxX1HtzHRLWR-RzSU8uXdxpX+vDzPT_-ZWjNedWsFtUw@mail.gmail.com>
 <CAPTjJmqTHsn0se=uh7AVUFuFGKZCr0GyG58pSwTpd1VCqOxnxw@mail.gmail.com>
 <CAKJDb-OvmN6yPg3JB5sBV-C72tQ5yh10eQs_Vq70OV0ewn4Xfw@mail.gmail.com>
Message-ID: <CAMpsgwZ+Ubi_MLG4nLHzpUM0JPOLxm1PZJ-T62QnTRQzPKQRCw@mail.gmail.com>

2017-05-09 18:11 GMT+02:00 Zachary Ware <zachary.ware+pydev at gmail.com>:
>> Agreed. Maybe a new list "buildbot-status at python.org"?
>
> I'd agree with this, or with using python-checkins at .  Dusty, commented
> code in the master config looks like notifications used to go there,
> but it was before my time and I don't know why it was stopped (if
> indeed it ever happened).

I'm not interested by python-checkins@, so at least me would like to
get two separated lists :-) It's not too difficult to subscribe to two
different lists ;-)

Victor

From ncoghlan at gmail.com  Tue May  9 22:03:50 2017
From: ncoghlan at gmail.com (Nick Coghlan)
Date: Wed, 10 May 2017 12:03:50 +1000
Subject: [Python-buildbots] Email notifications on buildbot failures
In-Reply-To: <CAKJDb-OvmN6yPg3JB5sBV-C72tQ5yh10eQs_Vq70OV0ewn4Xfw@mail.gmail.com>
References: <CAMpsgwaZ28GcR5_f1KAvcxWJ40yrVQ-o7iLDOSjQaT-L_deMTQ@mail.gmail.com>
 <CAGE7PNKxX1HtzHRLWR-RzSU8uXdxpX+vDzPT_-ZWjNedWsFtUw@mail.gmail.com>
 <CAPTjJmqTHsn0se=uh7AVUFuFGKZCr0GyG58pSwTpd1VCqOxnxw@mail.gmail.com>
 <CAKJDb-OvmN6yPg3JB5sBV-C72tQ5yh10eQs_Vq70OV0ewn4Xfw@mail.gmail.com>
Message-ID: <CADiSq7c98a6-zHTK2BJd1-VsOL6SSZmWn5LkWjU1wA3xOeZM5g@mail.gmail.com>

On 10 May 2017 at 02:11, Zachary Ware <zachary.ware+pydev at gmail.com> wrote:
> On Tue, May 9, 2017 at 11:04 AM, Chris Angelico <rosuav at gmail.com> wrote:
>> On Wed, May 10, 2017 at 1:43 AM, Gregory P. Smith <greg at krypto.org> wrote:
>>> Please do not send automated buildbot state transition mail to _this_
>>> list.  Leave this low traffic list to communication from humans about
>>> buildbots and infrastructure (the purpose as I understand it).
>
> That is indeed the intended purpose :)
>
>> Agreed. Maybe a new list "buildbot-status at python.org"?
>
> I'd agree with this, or with using python-checkins at .  Dusty, commented
> code in the master config looks like notifications used to go there,
> but it was before my time and I don't know why it was stopped (if
> indeed it ever happened).

My vague recollection is that it was originally turned on, but then
switched off for generating too many false alarms (i.e. problems with
the buildbots rather than problems with the test results). Separating
out a "stable" subset of buildbots that were expected to stay green
came later.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia