* [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-17
@ 2018-08-18 6:00 Thomas Petazzoni
2018-08-18 19:56 ` [Buildroot] Analysis of build " Thomas Petazzoni
0 siblings, 1 reply; 7+ messages in thread
From: Thomas Petazzoni @ 2018-08-18 6:00 UTC (permalink / raw)
To: buildroot
Hello,
Build statistics for 2018-08-17
===============================
branch | OK | NOK | TIM | TOT |
2018.02.x | 26 | 0 | 0 | 26 |
2018.05.x | 19 | 0 | 1 | 20 |
master | 173 | 15 | 2 | 190 |
next | 37 | 11 | 1 | 49 |
Results for branch '2018.05.x'
==============================
Classification of failures by reason
------------------------------------
host-libsodium | 1
Detail of failures
------------------
nios2 | host-libsodium | TIM | http://autobuild.buildroot.net/results/56f77e8a32d10fa0d4ac69ca00f3accef255bf1d |
Results for branch 'master'
===========================
Classification of failures by reason
------------------------------------
boost-1.67.0 | 8
host-guile-2.0.14 | 2
azure-iot-sdk-c | 1
f2fs-tools | 1
host-libselinux-2.7 | 1
micropython-v1.9.3 | 1
python-pyqt5-5.7 | 1
qt5base-5.11.1 | 1
samba4-4.8.4 | 1
Detail of failures
------------------
xtensa | azure-iot-sdk-c | TIM | http://autobuild.buildroot.net/results/bdf0360b0407acdbcf494e6efb4d76f772783f94 |
mipsel | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/6d3db8a67a1de75920624b3e13e8110e783ddbd9 |
mipsel | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/253bde162b4419a282f58f7932b0c6027ec6c742 |
arm | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/a256f3bfb9aceb3ed122beed39d9555a5cb07274 |
arm | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/212651b677cfb0763b34596d4f999103039d89bc |
arm | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/77f538992ea5f58245016f1a09fa5048895be19a |
m68k | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/97f9b0636d692571b9dcf38543ca79fc9de55bb7 |
sparc | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/37571087efdb4e1785ea94af8c56eddc1305f881 |
sparc | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/c830dc9cdbd4e08eda4ced4fa6213bff60c6706e |
arm | f2fs-tools | TIM | http://autobuild.buildroot.net/results/7d578300ff2c6c5e236c18eba7290739da245cc3 |
sparc | host-guile-2.0.14 | NOK | http://autobuild.buildroot.net/results/8546b7559e96ab0f3d2508722fd299e103e3457d | ORPH
mipsel | host-guile-2.0.14 | NOK | http://autobuild.buildroot.net/results/ba8a7dc1496ed9a63d408eb3d2683c485c273135 | ORPH
x86_64 | host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/d037515c949a377d4ace48b81675eb79e5964790 |
sh4 | micropython-v1.9.3 | NOK | http://autobuild.buildroot.net/results/2b18b9e1449f91d0c8d72ceadf298b5b37f5c9c4 |
aarch64 | python-pyqt5-5.7 | NOK | http://autobuild.buildroot.net/results/36598fac615b3f138e41e8dd1df903558cde765c |
or1k | qt5base-5.11.1 | NOK | http://autobuild.buildroot.net/results/a3535cdf5e91df011a59a4b9f60d69195f5efdcb |
mips64el | samba4-4.8.4 | NOK | http://autobuild.buildroot.net/results/1404a594583ff192d70086ef590f924472465c89 |
Results for branch 'next'
=========================
Classification of failures by reason
------------------------------------
boost-1.67.0 | 3
host-lvm2-2.02.180 | 3
qt5base-5.11.1 | 2
aircrack-ng-1.3 | 1
azure-iot-sdk-c | 1
mender-1.4.0 | 1
php-7.2.5 | 1
Detail of failures
------------------
powerpc | aircrack-ng-1.3 | NOK | http://autobuild.buildroot.net/results/d16ef6ca4968c3278ccba251aa8fa8be5f648c41 |
mipsel | azure-iot-sdk-c | TIM | http://autobuild.buildroot.net/results/13bb3f9302f8bf0bf3af9a5f248707596ea3520f |
nios2 | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/7165805e56a7f214e05253fd4c0a5ae1880d49ee |
nios2 | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/646dab37d383c7c539397fc07ef2b8a36163ceb8 |
powerpc | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/fb046c04fe18bec973d120e4ab33971f32ba5769 |
arm | host-lvm2-2.02.180 | NOK | http://autobuild.buildroot.net/results/33b567399d74d255f729a10bb3b2339563feef27 | ORPH
aarch64 | host-lvm2-2.02.180 | NOK | http://autobuild.buildroot.net/results/3299f39cd8b5c0bf70d7af0c496574fb4d8cc19d | ORPH
microblazeel | host-lvm2-2.02.180 | NOK | http://autobuild.buildroot.net/results/c3a0b2fae9a8f5353a0863b5812feea853d10fb8 | ORPH
powerpc64le | mender-1.4.0 | NOK | http://autobuild.buildroot.net/results/42a3f597d17ed4875f0d841f9c689a26d12c2086 |
mipsel | php-7.2.5 | NOK | http://autobuild.buildroot.net/results/9eeb555ada9f4fc001ebfeba76994768684bc5f0 | ORPH
or1k | qt5base-5.11.1 | NOK | http://autobuild.buildroot.net/results/b8192aa9cdd64ff6bb5bda57695f47856c3e7c97 |
aarch64_be | qt5base-5.11.1 | NOK | http://autobuild.buildroot.net/results/0ab70adbdb48f94ebedf337e3ad49f05ca9050f4 |
--
http://autobuild.buildroot.net
^ permalink raw reply [flat|nested] 7+ messages in thread* [Buildroot] Analysis of build results for 2018-08-17 2018-08-18 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-17 Thomas Petazzoni @ 2018-08-18 19:56 ` Thomas Petazzoni 2018-08-18 20:40 ` Chris Packham ` (2 more replies) 0 siblings, 3 replies; 7+ messages in thread From: Thomas Petazzoni @ 2018-08-18 19:56 UTC (permalink / raw) To: buildroot Hello, Hollis, Fabrice, Chris, Peter, there are some issues/questions for you below. On Sat, 18 Aug 2018 08:00:19 +0200 (CEST), Thomas Petazzoni wrote: > xtensa | azure-iot-sdk-c | TIM | http://autobuild.buildroot.net/results/bdf0360b0407acdbcf494e6efb4d76f772783f94 | Hollis autobuilder again failing to fetch. > mipsel | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/6d3db8a67a1de75920624b3e13e8110e783ddbd9 | > mipsel | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/253bde162b4419a282f58f7932b0c6027ec6c742 | static linking on MIPS for some reason pulls in the libboost_atomic library. I reported this to Fabrice already. > arm | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/a256f3bfb9aceb3ed122beed39d9555a5cb07274 | > arm | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/212651b677cfb0763b34596d4f999103039d89bc | Two other static linking configuration (on Cortex-M4) causing the same problem. > arm | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/77f538992ea5f58245016f1a09fa5048895be19a | > m68k | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/97f9b0636d692571b9dcf38543ca79fc9de55bb7 | > sparc | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/37571087efdb4e1785ea94af8c56eddc1305f881 | > sparc | boost-1.67.0 | NOK | http://autobuild.buildroot.net/results/c830dc9cdbd4e08eda4ced4fa6213bff60c6706e | These ones are fixed by: https://git.buildroot.org/buildroot/commit/?id=5f6f910cc9978910ebab5e088cb7c3870371b382 https://git.buildroot.org/buildroot/commit/?id=e2928dfa080658c35f6f0b7c9e62a3ade438a827 because the ARMv5, m68k and Sparc v8 architectures are now identified as not providing "always lock-free int atomics". > arm | f2fs-tools | TIM | http://autobuild.buildroot.net/results/7d578300ff2c6c5e236c18eba7290739da245cc3 | Another timeout issue on Hollis autobuilder. > sparc | host-guile-2.0.14 | NOK | http://autobuild.buildroot.net/results/8546b7559e96ab0f3d2508722fd299e103e3457d | ORPH > mipsel | host-guile-2.0.14 | NOK | http://autobuild.buildroot.net/results/ba8a7dc1496ed9a63d408eb3d2683c485c273135 | ORPH WARNING: 'makeinfo' is missing on your system. You should only need it if you modified a '.texi' file, or any other file indirectly affecting the aspect of the manual. You might want to install the Texinfo package: <http://www.gnu.org/software/texinfo/> The spurious makeinfo call might also be the consequence of using a buggy 'make' (AIX, DU, IRIX), in which case you might want to install GNU make: <http://www.gnu.org/software/make/> I'm not sure why this happens only on Hollis autobuilder. We had it with binutils/gdb in the past on other machines, so why does it happen for Guile, but only on Hollis autobuilder ? > x86_64 | host-libselinux-2.7 | NOK | http://autobuild.buildroot.net/results/d037515c949a377d4ace48b81675eb79e5964790 | This was fixed yesterday, but I messed up the commit, so I fixed it again: https://git.buildroot.org/buildroot/commit/?id=cb8d1743cab1449b91afbabe38c64cbb85bef6ba > sh4 | micropython-v1.9.3 | NOK | http://autobuild.buildroot.net/results/2b18b9e1449f91d0c8d72ceadf298b5b37f5c9c4 | cc1: warnings being treated as errors ../py/objdict.c: In function 'dict_view_print': ../py/objdict.c:458: error: dereferencing pointer 'o' does break strict-aliasing rules ../py/objdict.c:457: error: dereferencing pointer 'o' does break strict-aliasing rules ../py/objdict.c:456: error: dereferencing pointer 'o' does break strict-aliasing rules ../py/objdict.c:455: error: dereferencing pointer 'o' does break strict-aliasing rules ../py/objdict.c:454: note: initialized from here Not sure what is going on here, but it happens only on Hollis autobuilder: http://autobuild.buildroot.net/?reason=micropython% Chris, perhaps you have an idea ? > aarch64 | python-pyqt5-5.7 | NOK | http://autobuild.buildroot.net/results/36598fac615b3f138e41e8dd1df903558cde765c | This is due to a Qt method that has been removed in Qt 5.11. It can be fixed by applying https://src.fedoraproject.org/rpms/python-qt5/c/47fb7fdc5d16582772f9c3fc8a6a674a41a7f605?branch=master, but we need to find a way to make this conditional on Qt 5.11 (indeed with Qt 5.6, this should be preserved). > or1k | qt5base-5.11.1 | NOK | http://autobuild.buildroot.net/results/a3535cdf5e91df011a59a4b9f60d69195f5efdcb | Missing "double conversion" logic for OpenRISC. Peter (Seiderer), perhaps you could have a look ? At https://github.com/google/double-conversion/issues/73, the upstream maintainer was OK with testing happening in Qemu. > mips64el | samba4-4.8.4 | NOK | http://autobuild.buildroot.net/results/1404a594583ff192d70086ef590f924472465c89 | Fixed by https://git.buildroot.org/buildroot/commit/?id=6d3723147659542ec1cba4139981d75413d89edc Thomas -- Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] Analysis of build results for 2018-08-17 2018-08-18 19:56 ` [Buildroot] Analysis of build " Thomas Petazzoni @ 2018-08-18 20:40 ` Chris Packham 2018-08-18 20:56 ` Thomas Petazzoni 2018-08-18 22:37 ` Peter Seiderer 2018-08-19 18:59 ` Peter Korsgaard 2 siblings, 1 reply; 7+ messages in thread From: Chris Packham @ 2018-08-18 20:40 UTC (permalink / raw) To: buildroot On Sun, 19 Aug 2018, 7:56 AM Thomas Petazzoni, <thomas.petazzoni@bootlin.com> wrote: > > > sh4 | micropython-v1.9.3 | NOK | > http://autobuild.buildroot.net/results/2b18b9e1449f91d0c8d72ceadf298b5b37f5c9c4 > | > > > cc1: warnings being treated as errors > ../py/objdict.c: In function 'dict_view_print': > ../py/objdict.c:458: error: dereferencing pointer 'o' does break > strict-aliasing rules > ../py/objdict.c:457: error: dereferencing pointer 'o' does break > strict-aliasing rules > ../py/objdict.c:456: error: dereferencing pointer 'o' does break > strict-aliasing rules > ../py/objdict.c:455: error: dereferencing pointer 'o' does break > strict-aliasing rules > ../py/objdict.c:454: note: initialized from here > > Not sure what is going on here, but it happens only on Hollis autobuilder: > > http://autobuild.buildroot.net/?reason=micropython% > > Chris, perhaps you have an idea ? > I've tried reproducing this a few times with no luck. Initially I thought it was due to a newer gcc generating new warnings, but then I tried gcc 8 and didn't see any issue. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180819/37af0d52/attachment.html> ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] Analysis of build results for 2018-08-17 2018-08-18 20:40 ` Chris Packham @ 2018-08-18 20:56 ` Thomas Petazzoni 0 siblings, 0 replies; 7+ messages in thread From: Thomas Petazzoni @ 2018-08-18 20:56 UTC (permalink / raw) To: buildroot Hello, On Sun, 19 Aug 2018 08:40:55 +1200, Chris Packham wrote: > > Not sure what is going on here, but it happens only on Hollis autobuilder: > > > > http://autobuild.buildroot.net/?reason=micropython% > > > > Chris, perhaps you have an idea ? > > I've tried reproducing this a few times with no luck. Initially I thought > it was due to a newer gcc generating new warnings, but then I tried gcc 8 > and didn't see any issue. It happens only on Hollis autobuilder, which has the peculiarity of running an older RHEL6.5 distro, providing a gcc 4.4 host compiler, and general old tools. So it is probably in this direction that we should search, even if the problem apparently occurs when building code for the target. Best regards, Thomas -- Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] Analysis of build results for 2018-08-17 2018-08-18 19:56 ` [Buildroot] Analysis of build " Thomas Petazzoni 2018-08-18 20:40 ` Chris Packham @ 2018-08-18 22:37 ` Peter Seiderer 2018-08-19 18:59 ` Peter Korsgaard 2 siblings, 0 replies; 7+ messages in thread From: Peter Seiderer @ 2018-08-18 22:37 UTC (permalink / raw) To: buildroot Hello Thomas, On Sat, 18 Aug 2018 21:56:03 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote: > Hello, > > Hollis, Fabrice, Chris, Peter, there are some issues/questions for you > below. > > On Sat, 18 Aug 2018 08:00:19 +0200 (CEST), Thomas Petazzoni wrote: > [...] > > > or1k | qt5base-5.11.1 | NOK | http://autobuild.buildroot.net/results/a3535cdf5e91df011a59a4b9f60d69195f5efdcb | > > Missing "double conversion" logic for OpenRISC. Peter (Seiderer), > perhaps you could have a look ? At > https://github.com/google/double-conversion/issues/73, the upstream > maintainer was OK with testing happening in Qemu. $ cat div.c double Div_double(double x, double y) { return x / y; } $ cat main.c #include <stdio.h> double Div_double(double x, double y); int main(int argc, char** argv) { double result = Div_double(89255.0, 1e22); if (result == 89255e-22) { printf("correct result %e\n", result); return 1; } else { printf("wrong result %e\n", result); return 0; } } $ ./build_qemu_or1k_001/host/bin/or1k-buildroot-linux-uclibc-gcc -c main.c $ ./build_qemu_or1k_001/host/bin/or1k-buildroot-linux-uclibc-gcc -c div.c $ ./build_qemu_or1k_001/host/bin/or1k-buildroot-linux-uclibc-gcc -o main main.o div.o $ ./qemu-3.0.0-or1k-install/bin/qemu-or1k -L build_qemu_or1k_001/staging main correct result 8.925500e-18 Double-conversion test passed for or1k, buildroot qt5base patch will follow... Regards, Peter ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] Analysis of build results for 2018-08-17 2018-08-18 19:56 ` [Buildroot] Analysis of build " Thomas Petazzoni 2018-08-18 20:40 ` Chris Packham 2018-08-18 22:37 ` Peter Seiderer @ 2018-08-19 18:59 ` Peter Korsgaard 2018-08-19 19:26 ` Thomas Petazzoni 2 siblings, 1 reply; 7+ messages in thread From: Peter Korsgaard @ 2018-08-19 18:59 UTC (permalink / raw) To: buildroot >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes: Hi, >> aarch64 | python-pyqt5-5.7 | NOK | >> http://autobuild.buildroot.net/results/36598fac615b3f138e41e8dd1df903558cde765c >> | > This is due to a Qt method that has been removed in Qt 5.11. It can be > fixed by applying > https://src.fedoraproject.org/rpms/python-qt5/c/47fb7fdc5d16582772f9c3fc8a6a674a41a7f605?branch=master, > but we need to find a way to make this conditional on Qt 5.11 (indeed > with Qt 5.6, this should be preserved). I believe this can be done by checking QT_VERSION: https://doc.qt.io/qt-5/qtglobal.html#QT_VERSION -- Bye, Peter Korsgaard ^ permalink raw reply [flat|nested] 7+ messages in thread
* [Buildroot] Analysis of build results for 2018-08-17 2018-08-19 18:59 ` Peter Korsgaard @ 2018-08-19 19:26 ` Thomas Petazzoni 0 siblings, 0 replies; 7+ messages in thread From: Thomas Petazzoni @ 2018-08-19 19:26 UTC (permalink / raw) To: buildroot Hello, On Sun, 19 Aug 2018 20:59:33 +0200, Peter Korsgaard wrote: > > This is due to a Qt method that has been removed in Qt 5.11. It can be > > fixed by applying > > https://src.fedoraproject.org/rpms/python-qt5/c/47fb7fdc5d16582772f9c3fc8a6a674a41a7f605?branch=master, > > but we need to find a way to make this conditional on Qt 5.11 (indeed > > with Qt 5.6, this should be preserved). > > I believe this can be done by checking QT_VERSION: > > https://doc.qt.io/qt-5/qtglobal.html#QT_VERSION The SIP stuff that is used by PyQt to generate the binding also has a mechanism for conditional compilation depending on the Qt version. However, as explained in the patch I submitted to fix this issue [1], in the upstream PyQt5, they decided to drop entirely the support for this waitForEvents() method, even if PyQt5 is built against an older version of Qt than 5.11 (PyQt5 is full of conditionals depending on the Qt version, but they decided to not use that for waitForEvents). My patch follows what upstream did. Best regards, Thomas [1] http://patchwork.ozlabs.org/patch/959269/ -- Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2018-08-19 19:26 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2018-08-18 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-17 Thomas Petazzoni 2018-08-18 19:56 ` [Buildroot] Analysis of build " Thomas Petazzoni 2018-08-18 20:40 ` Chris Packham 2018-08-18 20:56 ` Thomas Petazzoni 2018-08-18 22:37 ` Peter Seiderer 2018-08-19 18:59 ` Peter Korsgaard 2018-08-19 19:26 ` Thomas Petazzoni
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox