[Development] Merge and Integration status report

Tue Jun 19 18:33:28 CEST 2018

Hi,

It is not a permission issue as far as I can see (literally).

Our best guess at the moment is that some underlying change caused a performance degradation. That combined with the fact that the CI runs all tests three times in debug-and-release configurations increases the changes of the failure aborting the integration enough to cause the blockage.

Ulf has now submitted a workaround that should also allow us to get an overview of running processes if it doesn't work. We've got a set of changes trying integration in 5.11 with that workaround merged and I'll try to get this also into dev.

Simon

________________________________
From: Tomasz Olszak <olszak.tomasz at gmail.com>
Sent: Saturday, June 16, 2018 12:59:46 PM
To: Simon Hausmann
Cc: Jani Heikkinen; development at qt-project.org
Subject: Re: [Development] Merge and Integration status report

Do you use up to date Win 10? Recent updates introduced many issue. E.g one of our app couldn't install with some privilege/policy access denied error. It was not clear from logs what happened. By trial and errors we just enabled camera for applications in security settings and it started to work. It might be good idea to reverse a few updates and check if it works.

sob., 16 cze 2018, 11:08 użytkownik Simon Hausmann <Simon.Hausmann at qt.io<mailto:Simon.Hausmann at qt.io>> napisał:
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 <Simon.Hausmann at qt.io<mailto:Simon.Hausmann at qt.io>> 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; development at qt-project.org<mailto: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<mailto:development-bounces+jani.heikkinen=qt.io at qt-project.org>> on behalf of Simon Hausmann <Simon.Hausmann at qt.io<mailto:Simon.Hausmann at qt.io>>
Sent: Thursday, June 14, 2018 10:32 AM
To: development at qt-project.org<mailto: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<mailto:development-bounces+simon.hausmann=qt.io at qt-project.org>> on behalf of Liang Qi <Liang.Qi at qt.io<mailto:Liang.Qi at qt.io>>
Sent: Thursday, June 14, 2018 9:18:32 AM
To: development at qt-project.org<mailto: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<mailto:Development at qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
Development at qt-project.org<mailto:Development at qt-project.org>
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
Development at qt-project.org<mailto: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/20180619/bcba7960/attachment.html>