From: Pedro Alves <palves@redhat.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: GDB 7.9.90 available for testing
Date: Fri, 10 Jul 2015 15:08:00 -0000 [thread overview]
Message-ID: <559FE003.5000205@redhat.com> (raw)
In-Reply-To: <CAGWvnynk6gw4jjtYF0j=8AGEnYVrz4V4P6r0cinYxpbOhZv4Zg@mail.gmail.com>
On 07/10/2015 03:56 PM, David Edelsohn wrote:
> My concern is more about GDB on Linux on z Systems and even GDB on
> x86-64, not AIX. AIX is weird.
>
> Shouldn't the buildbots for z Series and x86-64 be green before a release?
Ideally yes, but until the racy tests issue is fixed/kfailed and another
set of old known failures is kfail/xfailed, that can't happen.
I don't think any buildbot slave has ever been stably green yet; they
weren't green to start with. It used to be much worse a few months ago,
we're getting there, but it requires effort, and we could use all
the help we can get.
The buildbots are quite useful, but we can't rely on greenness
alone to determine release-readyness at the moment.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-07-10 15:08 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
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 [this message]
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=559FE003.5000205@redhat.com \
--to=palves@redhat.com \
--cc=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