[BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders

Sergio Durigan Junior sergiodj@redhat.com
Fri Dec 15 23:19:00 GMT 2017

On Friday, December 15 2017, David Edelsohn wrote:

> On Fri, Dec 15, 2017 at 4:19 PM, Yao Qi <qiyaoltc@gmail.com> wrote:
>> On Fri, Dec 15, 2017 at 2:34 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
>>> But the irony in your message should not be ignored.  You implicitly
>>> express that the buildbots are ignored, except possibly x86 and Try
>>> Builds on x86, while you proceed to ask for additional participation.
>> How do you get such implicit message?  That is your bias.  We still have
>> aarch64 and aarch32 buildslaves, they are quite stable, and catches
>> some build failures with g++ 4.8 and regressions.
>> These builders are disabled because they are useless.  Sergio asks for
>> participation to make these builders useful.  If no one wants to make these
>> builders better, or cares about them, it is reasonable to disable them.  It
>> is equivalent to code/feature/port deprecation, if nobody maintains the
>> code/feature/port, we'll deprecate it.
>>> This is fundamentally inconsistent.  Actions speak louder than words
>>> and this demonstrates the priorities of the GDB community.
>> I don't see the inconsistency here.  We need more participation or contribution
>> to make these builders more useful, it is simple, isn't?
> The buildbots are the responsibility of both the organization
> providing the servers and the community. No one from the community
> noticed anything wrong with the s390x debian buildbot for months. And
> no one said: "Hey, it looks like something is wrong with this
> buildbot, can the s390x community take a look?"  The message was: "The
> warning messages from the buildbot are annoying, so we're disabling
> them."


I contacted you back in private in October and let you know that your
buildslave was having issues.  The same way, by the way, that I also
contacted Edjunior about problems I was seeing with the PPC64 machines.

You replied to me with the same line you used here: "The machine is
fine, has lots of resources, there's nothing wrong".  Unfortunately I
could not dedicate more time to the issue I was seeing, but as Yao said,
s390x is not my priority and I thought it would be better to ask someone
else to have a look.  I assume you have more contact with the s390x
community than I do, but I don't know if you relayed my message to them
as well.

I will repeat: I did not disable the email notifications "because they
are annoying".  I disabled them because the Debian s390x, under your
supervision, have a backlog of more than 900 builds.  It is
counterproductive to let the notifications enabled in this case, because
(a) there is something clearly wrong happening, and (b) when a developer
asks for a Try Build, he/she expects the results e-mail to arrive in a
timely manner.

Anyway, I can't believe I'm having to explain these things again here.
So this will be my last post on this subject.

GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible

More information about the Gdb-patches mailing list