From: Jeff Law <law@redhat.com>
To: Andrew Pinski <pinskia@gmail.com>, Bernd Schmidt <bschmidt@redhat.com>
Cc: "Pinski, Andrew" <Andrew.Pinski@cavium.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: FW: Build failed in Jenkins: BuildThunderX_native_gcc_upstream #1267
Date: Fri, 17 Mar 2017 22:28:00 -0000 [thread overview]
Message-ID: <8e93562f-c69e-46b1-bede-7acdd859e8e0@redhat.com> (raw)
In-Reply-To: <CA+=Sn1=Mg6aDmiw1MX+STzRkvKd-1f5S4-PrREvkZtjan6shoQ@mail.gmail.com>
On 03/17/2017 03:31 PM, Andrew Pinski wrote:
> On Fri, Mar 17, 2017 at 11:47 AM, Bernd Schmidt <bschmidt@redhat.com> wrote:
>> On 03/17/2017 07:38 PM, Pinski, Andrew wrote:
>>>
>>> One of the following revision caused a bootstrap comparison failure on
>>> aarch64-linux-gnu:
>>> r246225
>>> r246226
>>> r246227
>>
>>
>> Can you help narrow that down?
>
> I can though I don't want to duplicate work since Jeff was going to
> provision an aarch64 system. My automated testing is approximately
> every hour or so; these commits were within an hour window even.
> I did not look into the revisions when I write the email but I suspect
> r246227 did NOT cause it since aarch64 does not use reload anymore.
My the box I got isn't terribly fast, but regardless I'll be walking
through each commit to see if I can trigger the failure.
246224 tested OK (as it should).
246225 is in progress.
jeff
>
next prev parent reply other threads:[~2017-03-17 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <258866171.579.1489773600679.JavaMail.jenkins@blackduck>
2017-03-17 18:39 ` Pinski, Andrew
2017-03-17 18:48 ` Bernd Schmidt
2017-03-17 19:33 ` Jeff Law
2017-03-17 21:31 ` Andrew Pinski
2017-03-17 22:28 ` Jeff Law [this message]
2017-03-17 23:12 ` Jim Wilson
2017-03-17 23:51 ` Jim Wilson
2017-03-18 1:32 ` Jeff Law
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=8e93562f-c69e-46b1-bede-7acdd859e8e0@redhat.com \
--to=law@redhat.com \
--cc=Andrew.Pinski@cavium.com \
--cc=bschmidt@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@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).