From: Joel Brobecker <brobecker@adacore.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: GDB 7.9.90 available for testing
Date: Fri, 10 Jul 2015 03:43:00 -0000 [thread overview]
Message-ID: <20150710034255.GB7406@adacore.com> (raw)
In-Reply-To: <CAGWvnyn342DKXnOdh+un86NaZaQ6d-Dd+XdSfEK1nNn3+OhL6Q@mail.gmail.com>
> I'm not certain if the baselines truly are accurate for all
> buildslaves, but it seems strange to create a release when the
> buildbot testsuite results show patches causing new failures.
To me, you are saying the same thing, and I don't disagree with you.
I said I didn't know that the buildBots were showing regressions.
Of course I would have held the creation of the branch if I had
known about this. But I didn't, and so here we are. Now we all know,
and the only way forward is to look at those regressions, and decide
what to do. We can and will delay the release if we have to.
Now, if you are implying that I didn't do enough as Release
Manager to prepare for this release, then that's an entirely
different discussion.
--
Joel
next prev parent reply other threads:[~2015-07-10 3:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 22:34 David Edelsohn
2015-07-09 23:21 ` Joel Brobecker
2015-07-10 1:30 ` David Edelsohn
2015-07-10 3:43 ` Joel Brobecker [this message]
2015-07-10 14:04 ` David Edelsohn
2015-07-10 14:33 ` Pedro Alves
2015-07-10 14:56 ` David Edelsohn
2015-07-10 15:08 ` Pedro Alves
2015-07-10 15:25 ` David Edelsohn
2015-07-10 15:33 ` Pedro Alves
2015-07-11 13:59 ` Doug Evans
2015-07-11 18:54 ` racy tests Pedro Alves
2015-07-14 16:05 ` Doug Evans
2015-07-14 20:26 ` Sergio Durigan Junior
-- strict thread matches above, loose matches on Subject: below --
2015-07-06 20:29 GDB 7.9.90 available for testing Joel Brobecker
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=20150710034255.GB7406@adacore.com \
--to=brobecker@adacore.com \
--cc=dje.gcc@gmail.com \
--cc=gdb-patches@sourceware.org \
/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