From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Jim Wilson <jim.wilson@linaro.org>
Cc: Yao Qi <qiyaoltc@gmail.com>, Pedro Alves <palves@redhat.com>,
gdb@sourceware.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: build bot failure
Date: Fri, 10 Jun 2016 18:47:00 -0000 [thread overview]
Message-ID: <87inxgvq3c.fsf@redhat.com> (raw)
In-Reply-To: <CABXYE2Xux5SW9CjOKtoU-ZSzQ6Z2fF0_tz5vZT95npJxj31wzw@mail.gmail.com> (Jim Wilson's message of "Fri, 10 Jun 2016 09:27:36 -0700")
On Friday, June 10 2016, Jim Wilson wrote:
> On Wed, May 25, 2016 at 1:07 AM, Yao Qi <qiyaoltc@gmail.com> wrote:
>> Pedro Alves <palves@redhat.com> writes:
>>
>>> Did you try the commit before Jim's? Maybe would helps determine whether
>>> this is a regression caused by Jim's patch, or some other issue with
>>> the slave's toolchain.
>>
>> Build is OK with the commit before Jim's.
>
> I haven't forgotten about this. I sent email asking for a compile
> farm account 2.5 weeks ago and got no response. I've pinged that
> mesage. I see that this is still broken in the build bot, but I won't
> be able to look at it until I get a compile farm account.
FWIW, I have just disabled e-mail notifications for the AIX machine (and
also for the RHEL-7.1 s390x). Their reports do not seem to be reliable,
so I don't think it's good to issue the warnings and waste time of the
developers.
I am Cc'ing David Edelsohn, who is the maintainer of both machines.
David, if you could take a look at them and fix these errors it'd be
awesome.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2016-06-10 18:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 0:40 Jim Wilson
2016-05-24 8:26 ` Yao Qi
2016-05-24 10:39 ` Yao Qi
2016-05-24 16:30 ` Jim Wilson
2016-05-24 16:48 ` Pedro Alves
2016-05-25 8:07 ` Yao Qi
2016-06-10 16:27 ` Jim Wilson
2016-06-10 18:47 ` Sergio Durigan Junior [this message]
2016-06-11 12:26 ` David Edelsohn
2016-06-11 17:00 ` Jim Wilson
2016-06-12 17:27 ` David Edelsohn
2016-06-22 23:15 ` Jim Wilson
2016-06-23 0:57 ` Sergio Durigan Junior
2016-11-14 11:06 ` Yao Qi
2016-11-14 13:01 ` David Edelsohn
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=87inxgvq3c.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gdb@sourceware.org \
--cc=jim.wilson@linaro.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@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