[Kmymoney-devel] Jenkins-kde-ci: alkimia master kf5-qt5 » Linux,gcc - Build # 3 - Still Unstable!

[Jack]

Going back to the original to reply, I can reproduce this, but my  
results are puzzling.

If I use "cmake -DCMAKE_BUILD_TYPE=Debug  
-DECM_ENABLE_SANITIZERS='address' -DBUILD_TESTING=ON  
-DSIP_DEFAULT_SIP_DIR=/home/jack/KDE/KMM/installframeworks/share/sip/  
-DCMAKE_INSTALL_PREFIX=/home/jack/KDE/KMM/installframeworks  
/usr/portage/tmpdir/portage/app-office/libalkimia-9999/work/libalkimia-9999"  
then I get the test failure.

If I omit the -DECM_ENABLE_SANITIZERS='address' I do not get the  
failure.

To try to figure this out, I did these two builds in parallel build  
directories, and then did a diff -r between them.  Dropping differences  
that are only with the build directory name, I see two differences very  
near the top of the diff output.

diff -r buildalkwith/CMakeCache.txt buildalkwithout/CMakeCache.txt
197,199d196
< //No help, variable specified on the command line.
< ECM_ENABLE_SANITIZERS:UNINITIALIZED=address
<
361c358
<  
alkimia_LIB_DEPENDS:STATIC=general;asan;general;Qt5::Core;general;Qt5::DBus;general;/usr/lib64/libgmp.so;
---
> alkimia_LIB_DEPENDS:STATIC=general;Qt5::Core;general;Qt5::DBus;general;/usr/lib64/libgmp.so;

diff -r buildalkwith/CMakeFiles/3.3.1/CMakeCCompiler.cmake  
buildalkwithout/CMakeFiles/3.3.1/CMakeCCompiler.cmake
4c4
< set(CMAKE_C_COMPILER_VERSION "4.9.3")
---
> set(CMAKE_C_COMPILER_VERSION "4.8.5")

I recently changed my profile for gcc from 4.8.5 to 4.9.3, but I  
completely logged out and in again before doing both of these builds,  
so I have no idea why one would be with the "old" profile.  Why would  
there be a difference in the gcc version used?  I wonder if these  
really used different versions of gcc, and if so, could that be the  
reason for the failure?  Otherwise, I wonder if I have some completely  
unrelated problem with my system.

Is there anything else I can try, or other info I can provide?

Jack


On 2015.12.03 14:03, Cristian Oneț wrote:
> If anyone can reproduce this failed test please let me know. It runs
> with success on my machine and I would not like to perform test
> debugging on the build machine using print statemements.
> 
> Regards,
> Cristian
> 
> 2015-12-03 20:30 GMT+02:00  <no-reply at kde.org>:
> >
> > GENERAL INFO
> >
> > BUILD UNSTABLE
> > Build URL:  
> https://build.kde.org/job/alkimia%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/3/
> > Project: PLATFORM=Linux,compiler=gcc
> > Date of build: Thu, 03 Dec 2015 18:28:36 +0000
> > Build duration: 2 min 1 sec
> >
> > CHANGE SET
> > Revision 0783adaf3ec9159dc09d384f5345f7f603ed47a7 by Cristian Oneț:  
> (Don't depend on KDELibs4Support to find GMP.)
> >   change: add cmake/modules/FindGMP.cmake
> >   change: edit CMakeLists.txt
> >
> >
> > JUNIT RESULTS
> >
> > Name: (root) Failed: 1 test(s), Passed: 2 test(s), Skipped: 0  
> test(s), Total: 3 test(s)Failed: TestSuite.alkvaluetest
> >
> > COBERTURA RESULTS
> >
> > Cobertura Coverage Report
> >   PACKAGES 1/1 (100%)FILES 9/9 (100%)CLASSES 9/9 (100%)LINE  
> 927/1012 (92%)CONDITIONAL 1750/3439 (51%)
> >
> > By packages
> >
> >         libalkimia
> >                 FILES 9/9 (100%)CLASSES 9/9 (100%)LINE 927/1012  
> (92%)CONDITIONAL 1750/3439 (51%)
> > _______________________________________________
> > KMyMoney-devel mailing list
> > KMyMoney-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/kmymoney-devel
> >
> _______________________________________________
> KMyMoney-devel mailing list
> KMyMoney-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kmymoney-devel
>