From: Kevin Hilman <khilman@baylibre.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kernel-build-reports@lists.linaro.org,
George Spelvin <linux@sciencehorizons.net>,
linux-kernel@vger.kernel.org,
"kernelci. org bot" <bot@kernelci.org>
Subject: Re: next build: 143 builds: 1 failed, 142 passed, 1 error, 22 warnings (next-20160801)
Date: Tue, 02 Aug 2016 11:55:31 -0700 [thread overview]
Message-ID: <m2lh0fq9uk.fsf@baylibre.com> (raw)
In-Reply-To: <2085340.PjMT6yBB6A@wuerfel> (Arnd Bergmann's message of "Mon, 01 Aug 2016 15:17:42 +0200")
Arnd Bergmann <arnd@arndb.de> writes:
> On Sunday, July 31, 2016 10:49:26 PM CEST kernelci. org bot wrote:
>> next build: 143 builds: 1 failed, 142 passed, 1 error, 22 warnings (next-20160801)
>>
>> Full Build Summary: https://kernelci.org/build/next/kernel/next-20160801/
>>
>> Tree: next
>> Branch: local/master
>> Git Describe: next-20160801
>> Git Commit: c24c1308a5b274bbd90db927cb18efddc95340c7
>> Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>> Built: 3 unique architectures
>>
>> Build Failure Detected:
>>
>> arm: gcc version 5.3.1 20160113 (Linaro GCC 5.3-2016.02)
>>
>> rpc_defconfig: FAIL
>
> I have verified that Linaro GCC 5.3-2016.05 is fixed, only Linaro GCC
> 5.3-2016.02 and earlier have this problem, please upgrade if possible
I don't see this packaged up yet. I'll upgrade as soon as it shows up
here:
https://releases.linaro.org/components/toolchain/binaries/latest-5/arm-linux-gnueabihf/
Thanks for testing and letting us know,
Kevin
prev parent reply other threads:[~2016-08-02 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <579ee2e6.68adc20a.8208b.b5be@mx.google.com>
2016-08-01 13:17 ` next build: 143 builds: 1 failed, 142 passed, 1 error, 22 warnings (next-20160801) Arnd Bergmann
2016-08-01 13:36 ` Mark Brown
2016-08-01 14:57 ` George Spelvin
2016-08-04 13:36 ` Geert Uytterhoeven
2016-08-04 14:49 ` George Spelvin
2016-08-04 14:58 ` Geert Uytterhoeven
2016-08-02 18:55 ` Kevin Hilman [this message]
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=m2lh0fq9uk.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=arnd@arndb.de \
--cc=bot@kernelci.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@sciencehorizons.net \
/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