From: David Edelsohn <dje.gcc@gmail.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
Edjunior Machado <emachado@redhat.com>
Subject: Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders
Date: Fri, 15 Dec 2017 13:54:00 -0000 [thread overview]
Message-ID: <CAGWvny=7UX1tOm+jQGhN2Pd=MsctxmRsFkg0Jj-6RUvBNfxvjg@mail.gmail.com> (raw)
In-Reply-To: <87d13g6r5t.fsf@redhat.com>
On Fri, Dec 15, 2017 at 8:45 AM, Sergio Durigan Junior
<sergiodj@redhat.com> wrote:
> Hi there,
>
> This is a small announcemente to let you know that I have disabled
> e-mail notifications for a few builders.
>
> All of the Fedora-ppc*-* builders:
>
> Fedora-ppc64be-m64
> Fedora-ppc64be-native-gdbserver-m64
> Fedora-ppc64be-native-extended-gdbserver-m64
> Fedora-ppc64be-cc-with-index
> Fedora-ppc64le-m64
> Fedora-ppc64le-native-gdbserver-m64
> Fedora-ppc64le-native-extended-gdbserver-m64
> Fedora-ppc64le-cc-with-index
>
> All of the Debian-s390x-* builders:
>
> Debian-s390x-m64
> Debian-s390x-native-gdbserver-m64
> Debian-s390x-native-extended-gdbserver-m64
>
> I have also removed them from the list of Try Builders, so if you use
> the try build, please update your config file. An updated list can be
> found here:
>
> <https://sourceware.org/gdb/wiki/BuildBot#Available_Builders>
>
> I took this decision after noticing that these builders have been
> lagging behind for quite some time. Some of them have more than 900
> queued builds!
>
> I've been talking with Edjunior Machado about the PPC64* machines.
> Unfortunately it appears that Minicloud, the project that provided the
> machines, is going through some difficulties right now. We're now
> investigating the possibility to move these resources to the GCC Compile
> Farm.
>
> As for the s390x machine, I haven't had the chance to investigate
> further what is happening.
>
> I would like to take this opportunity to invite more people/companies to
> join our BuildBot effort! There's always opportunity for improvement,
> and we're always looking for more machines and architectures to add to
> our infrastructure. If you have interest, please get in touch (in
> private) with me and we'll get the ball rolling.
This decision is beyond stupid and completely negates the purpose of
the buildbots. GDB testsuite now requieres 9 hours to complete on
s390x. Something is fundamentally broken. Instead of the GDB
community noticing the issue, investigating, and fixing, it chooses to
ignore the problem.
And yet you ask for more companies to participate and contribute build
bots. Why should any company participate when the response is pathetic
and issues that the buildbots raise are ignored? Companies should not
participate until the GDB community shows some interest in utilizing
and showing appreciation for the valuable resources contributed to the
program. Otherwise this is just a vanity project for Sergio with no
real benefit to the stability of GDB on the architectures, nor to the
companies.
Thanks, David
next prev parent reply other threads:[~2017-12-15 13:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 13:45 Sergio Durigan Junior
2017-12-15 13:54 ` David Edelsohn [this message]
2017-12-15 14:20 ` Sergio Durigan Junior
2017-12-15 14:34 ` David Edelsohn
2017-12-15 14:48 ` Pedro Alves
2017-12-15 15:06 ` David Edelsohn
2017-12-15 15:43 ` Pedro Alves
2017-12-15 15:53 ` David Edelsohn
2017-12-15 16:20 ` Pedro Alves
2017-12-15 17:29 ` David Edelsohn
2017-12-15 18:55 ` David Edelsohn
2017-12-15 19:20 ` Pedro Alves
2017-12-15 23:20 ` David Edelsohn
2017-12-18 19:21 ` Andreas Arnez
2017-12-15 14:49 ` Sergio Durigan Junior
2017-12-15 21:19 ` Yao Qi
2017-12-15 22:40 ` David Edelsohn
2017-12-15 23:19 ` Sergio Durigan Junior
2017-12-19 10:12 ` Joel Brobecker
2017-12-19 11:15 ` Yao Qi
2018-01-15 22:29 ` [BuildBot] Notifications re-enabled for the Debian-s390x-* builders (was: Re: [BuildBot] Notifications disabled for Debian-s390x-* and Fedora-ppc64*-* builders) Sergio Durigan Junior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGWvny=7UX1tOm+jQGhN2Pd=MsctxmRsFkg0Jj-6RUvBNfxvjg@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=emachado@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox