From: Thomas Schwinge <thomas@codesourcery.com>
To: Indu Bhagat <indu.bhagat@oracle.com>
Cc: "Martin Sebor" <msebor@gmail.com>,
"Martin Liška" <mliska@suse.cz>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
"Iain Sandoe" <iain@sandoe.co.uk>,
"Richard Biener" <richard.guenther@gmail.com>
Subject: Re: [PATCH] PR86957
Date: Tue, 11 Dec 2018 09:14:00 -0000 [thread overview]
Message-ID: <yxfpva4077da.fsf@hertz.schwinge.homeip.net> (raw)
In-Reply-To: <ec792945-9db4-ba2f-d9fe-5cab593a2808@oracle.com>
Hi Indu!
I recently saw that you just started contributing to GCC, so: welcome,
and enjoy to journey!
On Mon, 10 Dec 2018 12:54:09 -0800, Indu Bhagat <indu.bhagat@oracle.com> wrote:
> On 12/06/2018 05:54 PM, Indu Bhagat wrote:
> > [...]
Thanks for looking into this issue again. As I said in private email,
such things (like looking at the wrong build's test logs) happen to all
of us. As long as we learn -- or, at least try to learn ;-) -- something
from that, that's fine, as far as I'm concerned.
Evidently, the peer review/collaboration that we have in these Free
Software/Open Source software projects worked, and we eventually caught
this issue. :-)
> > 2. I do however see other tests (a total of 23) which are have
> > regressed from
> > PASS --> UNRESOLVED. A diff is attached.
> >
> > Each one of them is due to "Error/Warning threshold exceeded: 1 0
> > (max. 1 3)"
> False alarm.
>
> Looks like there is some flakiness I ran into.
Anything we could help you with, or that you have questions about?
> New testsuite runs (make check-gcc) on a fresh builds of the GCC (with
> and without missing-profile) enabled look OK.
> One additional failure as expected (Wmissing-profile.c). No additional
> unresolved tests.
Good, thanks for verifying!
Grüße
Thomas
next prev parent reply other threads:[~2018-12-11 9:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 19:29 Indu Bhagat
2018-09-11 9:21 ` Martin Liška
2018-09-16 8:28 ` Indu Bhagat
[not found] ` <159a29c5-8f8b-4194-dbea-1c9bd414db3a@oracle.com>
2018-09-17 10:10 ` Martin Liška
2018-09-17 11:20 ` Jan Hubicka
2018-09-18 19:41 ` Indu Bhagat
2018-09-21 23:23 ` Indu Bhagat
2018-09-24 16:46 ` Martin Sebor
2018-09-24 19:16 ` Indu Bhagat
2018-09-26 9:23 ` Martin Liška
2018-09-27 10:02 ` Richard Biener
2018-09-27 10:15 ` Martin Liška
2018-09-27 13:13 ` Martin Liška
2018-09-27 14:58 ` Richard Biener
2018-12-05 11:33 ` Thomas Schwinge
2018-12-07 1:46 ` Indu Bhagat
2018-12-10 20:45 ` Indu Bhagat
2018-12-11 9:14 ` Thomas Schwinge [this message]
2018-12-04 15:33 ` [committed, testsuite] Fix PR88310 Iain Sandoe
2018-09-11 9:23 ` [PATCH] PR86957 Martin Liška
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=yxfpva4077da.fsf@hertz.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
--cc=indu.bhagat@oracle.com \
--cc=mliska@suse.cz \
--cc=msebor@gmail.com \
--cc=richard.guenther@gmail.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).