[Development] Merge and Integration status report

Simon Hausmann Simon.Hausmann at qt.io
Thu Jun 14 10:53:13 CEST 2018


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; development at qt-project.org
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 <development-bounces+jani.heikkinen=qt.io at qt-project.org> on behalf of Simon Hausmann <Simon.Hausmann at qt.io>
Sent: Thursday, June 14, 2018 10:32 AM
To: development at qt-project.org
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 <development-bounces+simon.hausmann=qt.io at qt-project.org> on behalf of Liang Qi <Liang.Qi at qt.io>
Sent: Thursday, June 14, 2018 9:18:32 AM
To: development at qt-project.org
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
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20180614/d2b2d672/attachment.html>


More information about the Development mailing list