Re: [Development] CI is suffering from problems

2017-12-21 Thread Tony Sarajärvi 
Hi

This problem was fixed for now. We have the CI running again since yesterday 
afternoon. The system needed a cold boot of the server to update all disk 
related info after our cleanup. Free space etc were reported incorrectly before 
that.

To avoid this, we should never ever let the disk get 100% full, and we have to 
be more careful with that. Monitoring didn’t help here as we ignored the 
warnings we received ☹

-T
From: Tony Sarajärvi
Sent: torstai 21. joulukuuta 2017 14.19
To: development@qt-project.org
Subject: CI is suffering from problems

Hi

You have probably already noticed this, but here’s an email notifying you that 
we’re on it. Our OpenNebula isn’t able to clone any new virtual machines, 
complaining that the disk is full even though it isn’t. As said…we continue 
investigating.

Regards,
-Tony
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] CI is suffering from problems

2017-12-21 Thread Liang Qi 
both are known and fixes are available.

https://codereview.qt-project.org/#/c/215113/
https://codereview.qt-project.org/#/c/215046/

— Liang

> On 21 Dec 2017, at 14:17, Ulf Hermann  wrote:
> 
>> You have probably already noticed this, but here’s an email notifying
>> you that we’re on it. Our OpenNebula isn’t able to clone any new virtual
>> machines, complaining that the disk is full even though it isn’t. As
>> said…we continue investigating.
> 
> In addition to that we suddenly get failures when compiling QtCore and 
> QtNetwork, even if nothing has changed there:
> 
>> Module "qt/qtbase" (9ec8da01004481027df83361b998b24c63ab5a6d) The make 
>> execution failed. The CI rejected the staged commits due to the 
>> beforementioned reason. Possible reason could be flakiness in the system, 
>> but could also be a bug in one of the commits.:
>> /home/qt/work/qt/qtbase/src/corelib/global/qfloat16_f16c.c:61: undefined 
>> reference to `_mm256_cvtps_ph'
>> /home/qt/work/qt/qtbase/src/corelib/global/qfloat16_f16c.c:76: undefined 
>> reference to `_mm256_cvtph_ps'
>> Makefile:1152: recipe for target '../../lib/libQt5Core.so.5.11.0' failed
>> make[2]: *** [../../lib/libQt5Core.so.5.11.0] Error 1
>> make[1]: *** [sub-corelib-make_first] Error 2
>> make: *** [sub-src-make_first] Error 2
> 
> and
> 
>> Module "qt/qtbase" (99b12531013516c060eed60157f8b0be5eafa1e5) The make 
>> execution failed. The CI rejected the staged commits due to the 
>> beforementioned reason. Possible reason could be flakiness in the system, 
>> but could also be a bug in one of the commits.:
>> /opt/yocto-armv7/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-g++
>>  -c -include .pch/Qt5Network -pipe -march=armv7-a -mfpu=neon -DLINUX=1 
>> -mfloat-abi=hard 
>> --sysroot=/opt/yocto-armv7/sysroots/armv7ahf-neon-poky-linux-gnueabi -g 
>> -std=c++1z -fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions 
>> -Wall -W -Wvla -Wdate-time -Wshift-overflow=2 -Wduplicated-cond -Werror 
>> -Wno-error=cpp -Wno-error=deprecated-declarations -Wno-error=strict-overflow 
>> -D_REENTRANT -fPIC -DQT_NO_USING_NAMESPACE -DQT_NO_FOREACH 
>> -DQT_USE_SYSTEM_PROXIES -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT 
>> -DQT_BUILD_NETWORK_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII 
>> -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER 
>> -DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x05 
>> -DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_CORE_LIB 
>> -I. -Ikernel -I../../include -I../../include/QtNetwork 
>> -I../../include/QtNetwork/5.11.0 -I../../include/QtNetw
>> ork/5.11.0/QtNetwork -I../../include/QtCore/5.11.0 
>> -I../../include/QtCore/5.11.0/QtCore -I../../include/QtCore -I.moc 
>> -I../../mkspecs/devices/linux-imx7-g++ -o .obj/qnetworkinterface_linux.o 
>> kernel/qnetworkinterface_linux.cpp
>> kernel/qnetworkinterface_linux.cpp: In instantiation of ‘void 
>> {anonymous}::ProcessNetlinkRequest::operator()(int, nlmsghdr*, 
>> char*, size_t, Lambda&&) [with Lambda = getInterfaces(int, 
>> char*)::; size_t = unsigned int]’:
>> kernel/qnetworkinterface_linux.cpp:216:36:   required from ‘void 
>> {anonymous}::processNetlinkRequest(int, nlmsghdr*, char*, size_t, Lambda&&) 
>> [with Lambda = getInterfaces(int, char*)::; 
>> size_t = unsigned int]’
>> kernel/qnetworkinterface_linux.cpp:319:6:   required from here
>> kernel/qnetworkinterface_linux.cpp:161:48: error: comparison between signed 
>> and unsigned integer expressions [-Werror=sign-compare]
>> kernel/qnetworkinterface_linux.cpp: In instantiation of ‘void 
>> {anonymous}::ProcessNetlinkRequest::operator()(int, nlmsghdr*, 
>> char*, size_t, Lambda&&) [with Lambda = getAddresses(int, char*, 
>> QList&)::; size_t = 
>> unsigned int]’:
>> kernel/qnetworkinterface_linux.cpp:216:36:   required from ‘void 
>> {anonymous}::processNetlinkRequest(int, nlmsghdr*, char*, size_t, Lambda&&) 
>> [with Lambda = getAddresses(int, char*, 
>> QList&)::; size_t = 
>> unsigned int]’
>> kernel/qnetworkinterface_linux.cpp:423:6:   required from here
>> kernel/qnetworkinterface_linux.cpp:161:48: error: comparison between signed 
>> and unsigned integer expressions [-Werror=sign-compare]
>> Makefile:26401: recipe for target '.obj/qnetworkinterface_linux.o' failed
>> make[2]: *** [.obj/qnetworkinterface_linux.o] Error 1
>> make[1]: *** [sub-network-make_first] Error 2
>> make: *** [sub-src-make_first] Error 2
> 
> I guess in the first case the system headers changed and in the second case 
> the compiler changed. Do you actually test machine configuration changes 
> against the current state of Qt before you switch them live? I think that 
> should be done and any fixes to Qt for the new configuration should be 
> applied before the configuration goes live.
> 
> br,
> Ulf

Re: [Development] CI is suffering from problems

2017-12-21 Thread Ulf Hermann 

You have probably already noticed this, but here’s an email notifying
you that we’re on it. Our OpenNebula isn’t able to clone any new virtual
machines, complaining that the disk is full even though it isn’t. As
said…we continue investigating.


In addition to that we suddenly get failures when compiling QtCore and 
QtNetwork, even if nothing has changed there:



 Module "qt/qtbase" (9ec8da01004481027df83361b998b24c63ab5a6d) The make 
execution failed. The CI rejected the staged commits due to the beforementioned reason. 
Possible reason could be flakiness in the system, but could also be a bug in one of the 
commits.:
 /home/qt/work/qt/qtbase/src/corelib/global/qfloat16_f16c.c:61: undefined 
reference to `_mm256_cvtps_ph'
 /home/qt/work/qt/qtbase/src/corelib/global/qfloat16_f16c.c:76: undefined 
reference to `_mm256_cvtph_ps'
 Makefile:1152: recipe for target '../../lib/libQt5Core.so.5.11.0' failed
 make[2]: *** [../../lib/libQt5Core.so.5.11.0] Error 1
 make[1]: *** [sub-corelib-make_first] Error 2
 make: *** [sub-src-make_first] Error 2


and


Module "qt/qtbase" (99b12531013516c060eed60157f8b0be5eafa1e5) The make 
execution failed. The CI rejected the staged commits due to the beforementioned reason. 
Possible reason could be flakiness in the system, but could also be a bug in one of the 
commits.:
 
/opt/yocto-armv7/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-g++
 -c -include .pch/Qt5Network -pipe -march=armv7-a -mfpu=neon -DLINUX=1 
-mfloat-abi=hard 
--sysroot=/opt/yocto-armv7/sysroots/armv7ahf-neon-poky-linux-gnueabi -g 
-std=c++1z -fvisibility=hidden -fvisibility-inlines-hidden -fno-exceptions 
-Wall -W -Wvla -Wdate-time -Wshift-overflow=2 -Wduplicated-cond -Werror 
-Wno-error=cpp -Wno-error=deprecated-declarations -Wno-error=strict-overflow 
-D_REENTRANT -fPIC -DQT_NO_USING_NAMESPACE -DQT_NO_FOREACH 
-DQT_USE_SYSTEM_PROXIES -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT 
-DQT_BUILD_NETWORK_LIB -DQT_BUILDING_QT -DQT_NO_CAST_TO_ASCII 
-DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT -DQT_USE_QSTRINGBUILDER 
-DQT_DEPRECATED_WARNINGS -DQT_DISABLE_DEPRECATED_BEFORE=0x05 
-DQT_NO_EXCEPTIONS -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_CORE_LIB -I. 
-Ikernel -I../../include -I../../include/QtNetwork 
-I../../include/QtNetwork/5.11.0 -I../../include/QtNetw
 ork/5.11.0/QtNetwork -I../../include/QtCore/5.11.0 
-I../../include/QtCore/5.11.0/QtCore -I../../include/QtCore -I.moc 
-I../../mkspecs/devices/linux-imx7-g++ -o .obj/qnetworkinterface_linux.o 
kernel/qnetworkinterface_linux.cpp
 kernel/qnetworkinterface_linux.cpp: In instantiation of ‘void 
{anonymous}::ProcessNetlinkRequest::operator()(int, nlmsghdr*, char*, size_t, 
Lambda&&) [with Lambda = getInterfaces(int, char*)::; 
size_t = unsigned int]’:
 kernel/qnetworkinterface_linux.cpp:216:36:   required from ‘void 
{anonymous}::processNetlinkRequest(int, nlmsghdr*, char*, size_t, Lambda&&) [with 
Lambda = getInterfaces(int, char*)::; size_t = unsigned 
int]’
 kernel/qnetworkinterface_linux.cpp:319:6:   required from here
 kernel/qnetworkinterface_linux.cpp:161:48: error: comparison between signed 
and unsigned integer expressions [-Werror=sign-compare]
 kernel/qnetworkinterface_linux.cpp: In instantiation of ‘void 
{anonymous}::ProcessNetlinkRequest::operator()(int, nlmsghdr*, char*, size_t, Lambda&&) 
[with Lambda = getAddresses(int, char*, QList&)::; size_t = unsigned int]’:
 kernel/qnetworkinterface_linux.cpp:216:36:   required from ‘void 
{anonymous}::processNetlinkRequest(int, nlmsghdr*, char*, size_t, Lambda&&) [with Lambda = 
getAddresses(int, char*, QList&)::; size_t = unsigned int]’
 kernel/qnetworkinterface_linux.cpp:423:6:   required from here
 kernel/qnetworkinterface_linux.cpp:161:48: error: comparison between signed 
and unsigned integer expressions [-Werror=sign-compare]
 Makefile:26401: recipe for target '.obj/qnetworkinterface_linux.o' failed
 make[2]: *** [.obj/qnetworkinterface_linux.o] Error 1
 make[1]: *** [sub-network-make_first] Error 2
 make: *** [sub-src-make_first] Error 2


I guess in the first case the system headers changed and in the second 
case the compiler changed. Do you actually test machine configuration 
changes against the current state of Qt before you switch them live? I 
think that should be done and any fixes to Qt for the new configuration 
should be applied before the configuration goes live.


br,
Ulf
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] CI is suffering from problems

2017-12-21 Thread Tony Sarajärvi 
Hi

You have probably already noticed this, but here's an email notifying you that 
we're on it. Our OpenNebula isn't able to clone any new virtual machines, 
complaining that the disk is full even though it isn't. As said...we continue 
investigating.

Regards,
-Tony
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development