On Tuesday 26 of July 2016 15:30:48 Thiago Macieira wrote: > Em terça-feira, 26 de julho de 2016, às 23:24:21 PDT, Giuseppe D'Angelo > > escreveu: > > On Mon, Jul 25, 2016 at 5:51 PM, Thiago Macieira > > > > <thiago.macie...@intel.com> wrote: > > > Let's pay attention of what crashes and where. But we'll need to > > > reproduce > > > this in order to debug it. > > > > It just happened again: > > > > http://testresults.qt.io/logs/qt/qtbase/ddfe2ba984be5d652fe500f6695040959d > > b9 > > 8fa4/OSXOSX_10_11x86_64OSXOSX_10_11x86_64Clangqtci-osx-10.11-x86_64DebugA > > ndR > > elease_Release/85d6b000f945a84bc84a4f01f53ac65bc05cbe86/buildlog.txt.gz > This is a crash on Linux, with "core dumped", albeit in a unit test, not > moc: > > http://testresults.qt.io/logs/qt/qtbase/ > 47fa5811ef59b06d8d512b565db856c5c3bc5478/ > LinuxUbuntu_14_04x86_64LinuxUbuntu_14_04x86_64GCCqtci-linux-Ubuntu-14.04- > x86_64-be23deNoWidgets_ForceDebugInfo/ > 85d6b000f945a84bc84a4f01f53ac65bc05cbe86/testrun_1469528656/testlog.txt.gz > > Any chance we can get the backtrace of that crash?
No, the machine gets destroyed after test failure. Normally gdb session is attached to crashing process, that was not the case for some odd reason. Can it be that QTestLib is crashing too? There is feature request to upload core dumps (https://bugreports.qt.io/browse/QTQAINFRA-990) . Cheers, Jędrek _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
