From: Pedro Alves <palves@redhat.com>
To: David Edelsohn <dje.gcc@gmail.com>,
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 14:48:00 -0000 [thread overview]
Message-ID: <3808c9ac-450e-3d53-d5c6-ddd7f4b8d1df@redhat.com> (raw)
In-Reply-To: <CAGWvnynhBRuC1=r=PQxCuP1fwB6-eUVONAtLX2cGgAZJ8L9G_g@mail.gmail.com>
On 12/15/2017 02:34 PM, David Edelsohn wrote:
> I believe that the GDB buildbots should be useful to the GDB community
> and I appreciate your efforts to maintain it.
>
> 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.
> This is fundamentally inconsistent. Actions speak louder than words
> and this demonstrates the priorities of the GDB community.
I think there must be some misunderstanding here. IIUC, the problem with
the builders is not related at all to the quality of the PPC64 or s390
gdb ports. The problems are something else beyond GDB's control, they're
network, oversubscription, etc. problems, something like that. The builder
machines have simply not been able to exercise their basic function stably
enough, in turn causing problems for developers, instead of helping. What
can the community, as in, GDB maintainers, do, then? I for one have no
idea what I (just a developer) can do here. I think that the best course
of action is to disable reporting while investigations proceed, which I
understood it being exactly what is being done here. I don't think
Sergio deserved the reaction.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-12-15 14:48 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
2017-12-15 14:20 ` Sergio Durigan Junior
2017-12-15 14:34 ` David Edelsohn
2017-12-15 14:48 ` Pedro Alves [this message]
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=3808c9ac-450e-3d53-d5c6-ddd7f4b8d1df@redhat.com \
--to=palves@redhat.com \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).