From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-05-12
Date: Sat, 13 May 2017 14:20:58 +0200 [thread overview]
Message-ID: <dc955255-c483-c69b-588f-be53ad896fe3@gmail.com> (raw)
In-Reply-To: <20170513063125.BA761220BB@mail.free-electrons.com>
Le 13/05/2017 ? 08:31, Thomas Petazzoni a ?crit :
> Hello,
>
> Build statistics for 2017-05-12
> ================================
>
> successes : 232
> failures : 22
> timeouts : 0
> TOTAL : 254
>
> Classification of failures by reason
> ====================================
>
> opencv3-3.2.0 | 8
> libcdio-0.94 | 3
> rabbitmq-c-v0.8.0 | 2
> uclibc-ng-test-c9b9876cefc1... | 2
> domoticz-3.5877 | 1
> ffmpeg-3.3 | 1
> libcec-4.0.2 | 1
> mplayer-1.3.0 | 1
> openblas-f04af36ad0e85b64f1... | 1
> qt-4.8.7 | 1
> qt5webkit-5.8.0 | 1
>
>
> Detail of failures
> ===================
>
> nios2 | uclibc-ng-test-c9b9876cefc1... | NOK | http://autobuild.buildroot.net/results/d61c8d169fc070271114a515159650f7a0f333c0 |
> arm | uclibc-ng-test-c9b9876cefc1... | NOK | http://autobuild.buildroot.net/results/22295711046c519df44d5d976e0bfcae1f006e5a |
uclibc-ng broken with glibc 2.25 due to pthread_cond_t changes introduced by [1].
Waldemar has disabled this test (tst-cond22) with glibc based toolchain [2] but
the current uclibc-ng-test package doesn't contain this patch.
[1]
https://sourceware.org/git/?p=glibc.git;a=commit;h=ed19993b5b0d05d62cc883571519a67dae481a14
[2]
https://gogs.waldemar-brodkorb.de/linux/uclibc-ng-test/commit/787e584f18afc967d91cfe1a8443df2657579ecb
Best regards,
Romain
>
next prev parent reply other threads:[~2017-05-13 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 6:31 [Buildroot] [autobuild.buildroot.net] Build results for 2017-05-12 Thomas Petazzoni
2017-05-13 12:20 ` Romain Naour [this message]
2017-05-13 12:24 ` Thomas Petazzoni
2017-05-13 13:39 ` [Buildroot] Analysis of build " Thomas Petazzoni
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=dc955255-c483-c69b-588f-be53ad896fe3@gmail.com \
--to=romain.naour@gmail.com \
--cc=buildroot@busybox.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