Buildbot failures

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Buildbot failures

Antoine Pitrou

Hello,

There are currently a bunch of various buildbot failures on all 3
branches. I would remind committers to regularly take a look at the
buildbots, so that these failures get solved reasonably fast.

Regards

Antoine.


_______________________________________________
Python-Dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/lists%40nabble.com
Reply | Threaded
Open this post in threaded view
|

Re: Buildbot failures

andrea crotti-2
On 10/21/2011 10:08 PM, Antoine Pitrou wrote:
> Hello,
>
> There are currently a bunch of various buildbot failures on all 3
> branches. I would remind committers to regularly take a look at the
> buildbots, so that these failures get solved reasonably fast.
>
> Regards
>
> Antoine.

In my previous workplace if someone broke a build committing something
wrong he/she
had to bring cake for everyone next meeting.

The cake is not really feasible I guess, but isn't it possible to notify
the developer that
broke the build?

If one is not clearly defined, maybe notifying the last N developers
that committed
between the last successful builds and the failing build, would it be
possible and make sense?
_______________________________________________
Python-Dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/lists%40nabble.com
Reply | Threaded
Open this post in threaded view
|

Re: Buildbot failures

Antoine Pitrou

On Sat, 22 Oct 2011 20:30:34 +0100
Andrea Crotti <[hidden email]> wrote:
>
> In my previous workplace if someone broke a build committing something
> wrong he/she
> had to bring cake for everyone next meeting.
>
> The cake is not really feasible I guess, but isn't it possible to notify
> the developer that
> broke the build?

Some of us do the notifying manually, but it's quite boring
and bothersome.
Automating it is a bit tricky, since some of our tests (as well as some
of the buildslaves themselves) are a bit flaky and will produce
intermittent failures. But I think it's indeed the good direction.

Regards

Antoine.
_______________________________________________
Python-Dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/lists%40nabble.com
Reply | Threaded
Open this post in threaded view
|

Re: Buildbot failures

Nick Coghlan
In reply to this post by andrea crotti-2
On Sun, Oct 23, 2011 at 5:30 AM, Andrea Crotti
<[hidden email]> wrote:
> If one is not clearly defined, maybe notifying the last N developers that
> committed
> between the last successful builds and the failing build, would it be
> possible and make sense?

Yeah, as Antoine noted, that's where we want to get to eventually, but
at the moment, even the "stable" buildbots are a bit too flaky for us
to turn that on (essentially, the buildbots end up spamming the
alerts, so people start assuming they're *all* false alarms and the
notifications become ineffective). We're getting closer though - since
the buildbots were put in place, many of the flakier tests have been
redesigned to be significantly more reliable.

In the meantime, we rely on committers to check the buildbot pages for
a day or two after they make commits to confirm there aren't any
lurking cross-platforms problems or other issues with their changes.

Cheers,
Nick.

--
Nick Coghlan   |   [hidden email]   |   Brisbane, Australia
_______________________________________________
Python-Dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/lists%40nabble.com
Reply | Threaded
Open this post in threaded view
|

Re: Buildbot failures

briancurtin
In reply to this post by andrea crotti-2
On Sat, Oct 22, 2011 at 14:30, Andrea Crotti <[hidden email]> wrote:

> On 10/21/2011 10:08 PM, Antoine Pitrou wrote:
>>
>> Hello,
>>
>> There are currently a bunch of various buildbot failures on all 3
>> branches. I would remind committers to regularly take a look at the
>> buildbots, so that these failures get solved reasonably fast.
>>
>> Regards
>>
>> Antoine.
>
> In my previous workplace if someone broke a build committing something wrong
> he/she
> had to bring cake for everyone next meeting.
>
> The cake is not really feasible I guess, but isn't it possible to notify the
> developer that
> broke the build?

You just have to keep track and bring all of the cakes that you owe to PyCon.
_______________________________________________
Python-Dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/lists%40nabble.com
Reply | Threaded
Open this post in threaded view
|

Re: Buildbot failures

Stefan Behnel-3
Brian Curtin, 03.11.2011 15:59:

> On Sat, Oct 22, 2011 at 14:30, Andrea Crotti wrote:
>> On 10/21/2011 10:08 PM, Antoine Pitrou wrote:
>>>
>>> Hello,
>>>
>>> There are currently a bunch of various buildbot failures on all 3
>>> branches. I would remind committers to regularly take a look at the
>>> buildbots, so that these failures get solved reasonably fast.
>>>
>>> Regards
>>>
>>> Antoine.
>>
>> In my previous workplace if someone broke a build committing something wrong
>> he/she
>> had to bring cake for everyone next meeting.
>>
>> The cake is not really feasible I guess, but isn't it possible to notify the
>> developer that
>> broke the build?
>
> You just have to keep track and bring all of the cakes that you owe to PyCon.

Did you mean "PieCon"?

Stefan

_______________________________________________
Python-Dev mailing list
[hidden email]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/lists%40nabble.com