Build results for 2018-08-09
Hello,
Build statistics for 2018-08-09
===============================
branch | OK | NOK | TIM | TOT |
2018.02.x | 10 | 1 | 0 | 11 |
2018.05.x | 14 | 1 | 0 | 15 |
master | 123 | 10 | 3 | 136 |
next | 35 | 5 | 0 | 40 |Results for branch '2018.02.x'
==============================
Classification of failures by reason
------------------------------------
qt5webkit-5.9.1 | 1
Detail of failures
------------------
mipsel | qt5webkit-5.9.1 | NOK | http://autobuild.buildroot.net/results/c42a6e12e5f555bb8dda47e7144a74361dd41536 |
Results for branch '2018.05.x'
==============================
Classification of failures by reason
------------------------------------
qt5location-5.10.1 | 1
Detail of failures
------------------
mips64el | qt5location-5.10.1 | NOK | http://autobuild.buildroot.net/results/314462318bbc43cb5bd8f142455cb417a937c050 |
Results for branch 'master'
===========================
Classification of failures by reason
------------------------------------
f2fs-tools | 2
host-libselinux-2.7 | 2
ncmpc-0.30 | 2
azure-iot-sdk-c | 1
boost-1.67.0 | 1
moarvm-2017.05 | 1
python-pyqt5-5.7 | 1
qt5base-5.11.1 | 1
qt5location-5.11.1 | 1
qt5webkit-5.9.1 | 1 Detail of failures
------------------
mips64el | azure-iot-sdk-c | TIM | http://autobuild.buildroot.net/results/df878f5129d34e8916b9723db727ecfdbe4d1327 | m68k | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/bd77b0be062f273e336b4ef578d17b9c9bdd38cd | sparc | f2fs-tools | TIM | http://autobuild.buildroot.net/results/cf71468807f496a3d2fca1405989ebfce08a4900 | aarch64 | f2fs-tools | TIM | http://autobuild.buildroot.net/results/c826f38e321b999d0fc21ad9aae5e1d713f20417 | aarch64 | host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/66c03506e10071ec44ca509304595f4f5150e4d9 | mipsel | host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/2b41afe7841feba626fc29c9474e82d9934e6173 | powerpc64le | moarvm-2017.05 | NOK | http://autobuild.buildroot.net/results/c35ac4bbc5fb04aabf5a719eddeedf55f7f1f4eb | mips64el | ncmpc-0.30 | NOK | http://autobuild.buildroot.net/results/20942b594b08dabbfd6e14f4a2b257b2eb0a24e1 | mips64el | ncmpc-0.30 | NOK | http://autobuild.buildroot.net/results/13a079965b2b3d246a647152b6ec33e1ec5fd51b | arm | python-pyqt5-5.7 | NOK | http://autobuild.buildroot.net/results/d23103a6fa18cb77e14fa901e9475e53382be6db | aarch64_be | qt5base-5.11.1 | NOK | http://autobuild.buildroot.net/results/1fe2be0f26e5b92db57a5cfb5646dd253b731a5c | i686 | qt5location-5.11.1 | NOK | http://autobuild.buildroot.net/results/8b5531e44c4f4258c950902b2cd92d1ac8a8491e | mipsel | qt5webkit-5.9.1 | NOK | http://autobuild.buildroot.net/results/0fa860faa1cc5d007574bed4517c3e9db9ab389c |
Results for branch 'next'
=========================
Classification of failures by reason
------------------------------------
boost-1.67.0 | 3
host-gauche-0.9.5 | 1
mono-5.12.0.301 | 1 Detail of failures
------------------
sparc | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/0a2c7b4dce19bb4b08ad193ad1cd928e3586b65c | arm | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/1ab6781555aa875fa1e3c2cd583d0c2846916c21 | nios2 | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/269228fa1581dd4045777c3c7cafd8ec64a7658d | powerpc64 | host-gauche-0.9.5 | NOK | http://autobuild.buildroot.net/results/98b6d8dae4d774e9a860ccd139bca57c1653fce6 | arm | mono-5.12.0.301 | NOK | http://autobuild.buildroot.net/results/1ca8d9a12e6b816127f35f653580e2ca64f1c0d5 |
Signature · 1 line
http://autobuild.buildroot.net
[Buildroot] Analysis of build results for 2018-08-09
Hello,
Quoted 7 lines · Thomas Petazzoni
Build statistics for 2018-08-09
===============================branch | OK | NOK | TIM | TOT | 2018.02.x | 10 | 1 | 0 | 11 | 2018.05.x | 14 | 1 | 0 | 15 | master | 123 | 10 | 3 | 136 |
This we've got only 10 failures on master, let's have a look at them.
Quoted 1 line
m68k | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/bd77b0be062f273e336b4ef578d17b9c9bdd38cd |
This is another instance of "libboost_atomic shouldn't have been
installed: missing select in boost/Config.in". Fabrice, you had sent patches for this, but I made some comments explaining the patches were not correct. Do you intend to work on this again in the near future ?
Quoted 2 lines
sparc | f2fs-tools | TIM | http://autobuild.buildroot.net/results/cf71468807f496a3d2fca1405989ebfce08a4900 | aarch64 | f2fs-tools | TIM | http://autobuild.buildroot.net/results/c826f38e321b999d0fc21ad9aae5e1d713f20417 |
Hollis: your autobuilder is consistently timing out on f2fs-tools, during the download step:
http://autobuild.buildroot.net/?reason=f2fs-tools. Could you investigate what's going on ?
Quoted 2 lines
aarch64 | host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/66c03506e10071ec44ca509304595f4f5150e4d9 | mipsel | host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/2b41afe7841feba626fc29c9474e82d9934e6173 |
Due to the use of atomic built-ins, not available in old compilers. I would suggest to make all packages that depend on host-libselinux to depend on the appropriate host gcc version.
Quoted 1 line
powerpc64le | moarvm-2017.05 | NOK | http://autobuild.buildroot.net/results/c35ac4bbc5fb04aabf5a719eddeedf55f7f1f4eb |
dyncall_call_ppc64.S: Assembler messages:
dyncall_call_ppc64.S:135: Error: operand out of range (5 is not between 0 and 1) dyncall_call_ppc64.S:135: Error: missing operand
Fran?ois, could you report this upstream ?
Quoted 2 lines
mips64el | ncmpc-0.30 | NOK | http://autobuild.buildroot.net/results/20942b594b08dabbfd6e14f4a2b257b2eb0a24e1 | mips64el | ncmpc-0.30 | NOK | http://autobuild.buildroot.net/results/13a079965b2b3d246a647152b6ec33e1ec5fd51b |
Weird C++ issue, occurring since a while:
http://autobuild.buildroot.net/?reason=ncmpc-0.30. Fabrice, you're listed in the DEVELOPERS file for ncmpc, could you have a look ?
Quoted 1 line
arm | python-pyqt5-5.7 | NOK | http://autobuild.buildroot.net/results/d23103a6fa18cb77e14fa901e9475e53382be6db |
/home/naourr/work/instance-1/output/build/python-pyqt5-5.7/QtTest/sipQtTestQTest.cpp: In function 'PyObject* meth_QTest_waitForEvents(PyObject*, PyObject*)':/home/naourr/work/instance-1/output/build/python-pyqt5-5.7/QtTest/sipQtTestQTest.cpp:263:20: error: 'waitForEvents' is not a member of 'QTest'
QTest::waitForEvents();
Manuel, you added support for python-pyqt5. Could you have a look at this ?
Quoted 1 line
aarch64_be| qt5base-5.11.1 | NOK | http://autobuild.buildroot.net/results/1fe2be0f26e5b92db57a5cfb5646dd253b731a5c |
This is just about adapting the Double-Conversion header to support AArch64 BE.
Quoted 1 line
i686 | qt5location-5.11.1 | NOK | http://autobuild.buildroot.net/results/8b5531e44c4f4258c950902b2cd92d1ac8a8491e |
Some crazy C++ error. Peter (Seiderer), could you have a look ?
Quoted 1 line
mipsel | qt5webkit-5.9.1 | NOK | http://autobuild.buildroot.net/results/0fa860faa1cc5d007574bed4517c3e9db9ab389c |
Some crazy MIPS issue. We simply need to disable on the problematic MIPS sub-architecture. The same issue was already reported in February 2016 in
http://lists.busybox.net/pipermail/buildroot/2016-February/153612.html,
we were using qt5webkit 5.5 back then. The issue still hasn't been resolved, so let's disable this package on MIPS32r6 and MIPS64r6.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com
[Buildroot] Analysis of build results for 2018-08-09
Thomas,
Quoted 13 lines · Thomas Petazzoni
Hello,
Quoted 7 lines · Thomas Petazzoni
Build statistics for 2018-08-09
===============================branch | OK | NOK | TIM | TOT | 2018.02.x | 10 | 1 | 0 | 11 | 2018.05.x | 14 | 1 | 0 | 15 | master | 123 | 10 | 3 | 136 |
Quoted 7 lines
This we've got only 10 failures on master, let's have a look at them.
Quoted 2 lines
aarch64 | host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/66c03506e10071ec44ca509304595f4f5150e4d9 | mipsel | host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/2b41afe7841feba626fc29c9474e82d9934e6173 |Due to the use of atomic built-ins, not available in old compilers. I would suggest to make all packages that depend on host-libselinux to depend on the appropriate host gcc version.
Hollis has sent a patch suggestion to keep libselinux compatible with older gcc. Is there a preference on carrying the patch vs using a host gcc version detect ? I didn't realize we had a way to depend on host gcc version. I'll take a look at that but let me know which way is preferred.
Matt
[Buildroot] Analysis of build results for 2018-08-09
Hello,
Adding Hollis, which I forgot in my initial e-mail. Hollis, please have a look at the thread, there has been some other build errors on your older build machine.
Quoted 8 lines · Matthew Weber
Quoted 7 lines
This we've got only 10 failures on master, let's have a look at them.
Quoted 2 lines
aarch64 | host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/66c03506e10071ec44ca509304595f4f5150e4d9 | mipsel | host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/2b41afe7841feba626fc29c9474e82d9934e6173 |Due to the use of atomic built-ins, not available in old compilers. I would suggest to make all packages that depend on host-libselinux to depend on the appropriate host gcc version.
Quoted 5 lines
Hollis has sent a patch suggestion to keep libselinux compatible with older gcc. Is there a preference on carrying the patch vs using a host gcc version detect ? I didn't realize we had a way to depend on host gcc version. I'll take a look at that but let me know which way is preferred.
If the issue can be worked around by a patch, it's nice because we don't have to propagate the host gcc dependency to gazillions of packages. However, Hollis patch wasn't that simple/trivial, it would be nice to have it checked by upstream. Or maybe it's just me who isn't familiar enough with the semantic of atomic intrinsics.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com
[Buildroot] Analysis of build results for 2018-08-09
In reply to Thomas PetazzoniHello *,
Quoted 3 lines · Thomas Petazzoni
Hello,
On Fri, 10 Aug 2018 08:00:17 +0200 (CEST), Thomas Petazzoni wrote:
[...]
Quoted 5 lines
Quoted 2 lines
aarch64_be| qt5base-5.11.1 | NOK | http://autobuild.buildroot.net/results/1fe2be0f26e5b92db57a5cfb5646dd253b731a5c |This is just about adapting the Double-Conversion header to support AArch64 BE.
Fixed by [1], compiles fine with the patch applied and using a buildroot AArch64 BE generated toolchain...
Quoted 4 lines
Quoted 1 line
i686 | qt5location-5.11.1 | NOK | http://autobuild.buildroot.net/results/8b5531e44c4f4258c950902b2cd92d1ac8a8491e |Some crazy C++ error. Peter (Seiderer), could you have a look ?
No clue either, maybe the used compiler
$ ./host/bin/i686-ctng-linux-gnu-g++ --version
i686-ctng-linux-gnu-g++ (crosstool-NG hg+-c65fcf8a34b7) 4.8.2is to old for the c++11 [2] QPointer<QGeoMap> and QOverload<const QString &>::of(&QGeoMap::copyrightsChanged) dance for the connect?
Regards,
Peter
[1] https://patchwork.ozlabs.org/patch/957169/
[2] http://doc.qt.io/qt-5/qtglobal.html#qOverload