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]> on behalf of Liang Qi <[email protected]> Sent: Thursday, June 14, 2018 9:18:32 AM To: [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] http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
