[Development] CI upgrade

Tony Sarajärvi tony.sarajarvi at qt.io
Wed Jan 2 07:34:43 CET 2019


Hi

I'd like to know your opinion about these failures we've been seeing during the last 24 hours. Are they related to QEMU being updated perhaps?

on RHEL 7.4:
agent:2019/01/01 20:15:25 build.go:193: /home/qt/work/install/bin/qmltestrunner
agent:2019/01/01 20:15:26 build.go:193: ********* Start testing of qmltestrunner *********
agent:2019/01/01 20:15:26 build.go:193: Config: Using QtTest library 5.12.0, Qt 5.12.0 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.3.1 20160406 (Red Hat 5.3.1-6))
agent:2019/01/01 20:15:26 build.go:193: PASS   : qmltestrunner::shadersource-dynamic-sourceobject::initTestCase()
agent:2019/01/01 20:15:26 build.go:193: BPASS  : qmltestrunner::shadersource-dynamic-sourceobject::test_endresult()
agent:2019/01/01 20:15:26 build.go:193: PASS   : qmltestrunner::shadersource-dynamic-sourceobject::cleanupTestCase()
agent:2019/01/01 20:15:26 build.go:193: PASS   : qmltestrunner::shadersource-dynamic-shadersource::initTestCase()
agent:2019/01/01 20:15:26 build.go:193: make: *** [check] Segmentation fault (core dumped)

on Windows 10:
agent:2019/01/01 03:56:28 build.go:193:                           call C:\Users\qt\work\qt\qt3d\tests\auto\render\qrendertargetoutput\target_wrapper.bat  release\tst_qrendertargetoutput.exe -o C:\Users\qt\work\testresults\tests\auto\render\qrendertargetoutput782111623,xml -o -,txt
agent:2019/01/01 03:56:28 build.go:193: jom: C:\Users\qt\work\qt\qt3d\tests\auto\render\qrendertargetoutput\Makefile.Release [check] Error 2
agent:2019/01/01 03:56:28 build.go:193: jom: C:\Users\qt\work\qt\qt3d\tests\auto\render\qrendertargetoutput\Makefile [release-check] Error 2
agent:2019/01/01 03:56:28 build.go:237: Process finished with error: exit status 2
agent:2019/01/01 03:56:28 build.go:196: Error reading from stdout/err: exit status 2
agent:2019/01/01 03:56:28 build.go:435: Executing scheduled instruction 1 of 2 - Upload all core dumps if there are some

I also reported these 3 autotest crashes before we switched over to the new software stack:
https://bugreports.qt.io/browse/QTBUG-72781
https://bugreports.qt.io/browse/QTBUG-72782
https://bugreports.qt.io/browse/QTBUG-72790

-Tony
From: Tony Sarajärvi <tony.sarajarvi at qt.io>
Sent: maanantai 31. joulukuuta 2018 8.28
To: development at qt-project.org
Subject: CI upgrade

Good morning.

Since our last verifications of 3 main branches show green light to make the upgrade of the CI, I'll go ahead and proceed right away. The switch over will only take seconds, and I'll start monitoring the system today to see that it actually works.

What changes:

  *   Our hosts running the virtual machines get updated from Ubuntu 17.10.x -> 18.04.x (Maintained by MAAS and its PXE boot)
     *   libvirt and QEMU API versions get updated from 3.6.0 -> 4.0.0
     *   Hypervisor from QEMU 2.10.1 -> 2.11.1
  *   OpenNebula 5.4.1 -> 5.4.13
  *   MAAS 2.2.2 -> 2.4.2
     *   And the host MAAS runs on from Ubuntu 16.04.3 -> 18.04.1

Most of all we have high hopes that these new versions will bring a lot of stability to the CI.

-Tony


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20190102/81a506f0/attachment.html>


More information about the Development mailing list