From: Dennis Clarke <dclarke@blastwave.org>
To: gdb@sourceware.org
Subject: Re: Very messy results from testsuite in GDB 8.1
Date: Mon, 05 Feb 2018 22:40:00 -0000 [thread overview]
Message-ID: <705e5846-7792-4fc0-4275-e2216802ae43@blastwave.org> (raw)
In-Reply-To: <CAH=s-PMtw-ePJihO2LGXWCw9ci2_ECcHEJdjz2-oonE+ad-Gwg@mail.gmail.com>
On 05/02/18 05:20 PM, Yao Qi wrote:
> On Mon, Feb 5, 2018 at 8:06 PM, Dennis Clarke <dclarke@blastwave.org> wrote:
>> I was saddened to see these results of the 8.1 testsuite :
>>
>> I will move onwards to a Red Hat Enterprise Linux 7.4 system and see
>> what results happen there but for the moment I have to ask if other
>> people are seeing reasonable build and testsuite results?
>
> We have buildbot ppc64 slaves. I am not clear on these ppc64 machine
> details, but the number of fails is similar to what you get now.
> https://gdb-build.sergiodj.net/builders/CentOS-ppc64be-m64/builds/101/steps/regressions/logs/stdio
That causes me to think that I can not yet use gdb 8.1.x on ppc64.
Dennis
next prev parent reply other threads:[~2018-02-05 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 20:06 Dennis Clarke
2018-02-05 22:20 ` Yao Qi
2018-02-05 22:40 ` Dennis Clarke [this message]
2018-02-06 4:18 ` Joel Brobecker
2018-02-06 18:15 ` Dennis Clarke
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=705e5846-7792-4fc0-4275-e2216802ae43@blastwave.org \
--to=dclarke@blastwave.org \
--cc=gdb@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