Hi, Unfortunately we haven’t found a solution or workaround yet - the module remains blocked.
We can observe some virtual machines slowing down to a grinding halt and we can observe that quite often at boot time. The latter causes the CI to kill the vm after some time and try creating a new one. That story repeats itself until finally a situation/host is found where everything works. This also makes overall integration times slower. We can also observe how every test in debug-and-release is run three times and with flaky tests as in this case that increases the probability of an overall failure and it increases the overall time to test for all projects. What nobody has managed to do so far is reproduce the declarative failure in front of human eyes. Whenever observed through the hypervisor’s vnc interface it appears to work smoothly. One thing that is unclear to me is what exactly has changed that causes this, because I think that given the spread across branches it was not a change in declarative or qtbase. Unfortunately we do not have a journal of sorts that records what changes were done on the infrastructure at what time. It might even be an innocent change that triggered an actual bug in declarative. Does anybody see odd test failures that seem performance related in other modules, across branches? Simon On 14. Jun 2018, at 10:53, Simon Hausmann <[email protected]<mailto:[email protected]>> wrote: Yes, that is another issue. But before that qtbase issue started showing up, the same change to 5.11.1 that you're trying to integrated failed when running a test that launches a separate process of testing the debugging integration. So once the qtbase issue is resolved it's likely that you'll run into the declarative failure again. Simon ________________________________ From: Jani Heikkinen Sent: Thursday, June 14, 2018 10:47:43 AM To: Simon Hausmann; [email protected]<mailto:[email protected]> Subject: Re: Merge and Integration status report Actually at least 5.11.1 declarative integration failure is timeout in qtbase -> Linux QEMU (gcc-armv7) build. So the failure is different there (in case it helps anything) br, Jani ________________________________________ From: Development <[email protected]<mailto:[email protected]>> on behalf of Simon Hausmann <[email protected]<mailto:[email protected]>> Sent: Thursday, June 14, 2018 10:32 AM To: [email protected]<mailto:[email protected]> Subject: Re: [Development] Merge and Integration status report Hi, Thank you Liang for the report. On top of that, qtdeclarative is not accepting any changes in the 5.9, 5.11, 5.11.1 and dev branches right now. Those who may have tried staging changes there may have noticed that they are failing in one of the tests that launch a separate process for testing the debugging integration, limited to Windows 10 (x86 and x86-64). Until we've found the root cause or a suitable workaround, please don't stage changes to qtdeclarative. I can't see any recent common changes to qtbase or declarative that apply to all _four_ branches, so I suspect this flaky issue was caused by something below those two modules. I'll post an update here when we've figured it out (workaround or solution). Simon ________________________________ From: Development <[email protected]<mailto:[email protected]>> on behalf of Liang Qi <[email protected]<mailto:[email protected]>> Sent: Thursday, June 14, 2018 9:18:32 AM To: [email protected]<mailto:[email protected]> Subject: [Development] Merge and Integration status report Integrations * qt5 dev integration failed from June 2, a submodule update without qtdeclarative was done on June. 9 * * Issue: https://bugreports.qt.io/browse/QTBUG-68666 declarative_core::MappingManagerError::test_error() failed * * * https://codereview.qt-project.org/#/c/222768 Simon is working on that since yesterday * qt5 5.11 integration failed from June 9 * * Issue: https://bugreports.qt.io/browse/QTBUG-68773 qtwayland build failed - can't find some headers * * * https://codereview.qt-project.org/#/c/232288/ Robert Griebl has a fix, Oswald please help to review it. * * Issue: https://bugreports.qt.io/browse/QTBUG-68741 tst_QQmlDebuggingEnabler::qmlscene() failed _______________________________________________ Development mailing list [email protected]<mailto:[email protected]> http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected]<mailto:[email protected]> http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
