Em quarta-feira, 3 de maio de 2017, às 05:08:49 PDT, Edward Welbourne escreveu: > Thiago Macieira wrote: > >> In 5.8, the build deadlocks, so > >> we can't even just disable a test. > > René J. V. Bertin (3 May 2017 13:28) replied: > > How is that even possible? > > We don't know. And yet: > > https://testresults.qt.io/logs/qt/qtbase/74dfb52faa8370b61de9eb89947bfdd473f > e4986/LinuxUbuntu_15_04x86_64LinuxUbuntuTouch_15_04armv7GCCqtci-linux-Ubuntu > -15.04-x86_64-6e07ddDisableTests_OpenGLES2/85d6b000f945a84bc84a4f01f53ac65bc > 05cbe86/buildlog.txt.gz > > ... apparently repeatably. So Thiago is, understandably, reticent about > moving forward until we can make sense of it.
I could start firing in the dark. For example, one characteristic of the above build that never matches any of my local tests is that it's a cross- compilation to ARM. So we could disable QtDBus by default when cross- compiling. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
