From: Joel Brobecker <brobecker@adacore.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
gdb-buildbot@sergiodj.net, GDB <gdb-patches@sourceware.org>
Subject: Re: Oh dear. I regret to inform you that commit b1308d2c3749cc454f00b70768ee33724d919527 might be unfortunate
Date: Thu, 07 Sep 2017 23:35:00 -0000 [thread overview]
Message-ID: <20170907233459.va2wfui2reysz3h2@adacore.com> (raw)
In-Reply-To: <CAMe9rOrcaWNidCLUsYTNgNNCY-nwuS8QJvW9WygFCixod9AUcw@mail.gmail.com>
> This bot is next to useless. I just ignore it.
>
> This bot shouldn't spam people when the new commit doesn't change
> the old error.
Personally, I think it is great that we have a buildbot that tests
so many configurations and platforms. This is a great tool and
while there are issues today, I really don't think we should be
ignoring them. The right thing to do was to report/ask here, which
led to Sergio immediately jumping on it. Thank you Sergio!
This buildbot is really there to help us out discover regressions
soon after we commit, when it's easier to investigate and adjust,
or revert if necessary. While we get annoyed sometime, it's still
going to benefit us all. Let's encourage its improvement, and offer
our help to its development team, rather than denigrate it.
--
Joel
next prev parent reply other threads:[~2017-09-07 23:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1dq0Uz-00056v-Ti@kwanyin.sergiodj.net>
2017-09-07 17:56 ` Palmer Dabbelt
2017-09-07 18:00 ` H.J. Lu
2017-09-07 18:57 ` Sergio Durigan Junior
2017-09-07 19:32 ` H.J. Lu
2017-09-07 19:41 ` Sergio Durigan Junior
2017-09-07 19:52 ` H.J. Lu
2017-09-07 19:54 ` Sergio Durigan Junior
2017-09-07 19:57 ` Sergio Durigan Junior
2017-09-07 23:35 ` Joel Brobecker [this message]
2017-09-08 2:10 ` H.J. Lu
2017-09-08 5:41 ` Sergio Durigan Junior
2017-09-07 18:52 ` Sergio Durigan Junior
2017-09-10 5:54 ` 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=20170907233459.va2wfui2reysz3h2@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=palmer@dabbelt.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