Re: [Development] Merge and Integration status report - 2019.09.06
During the weekend, qt5 dev and 5.15 got integrated. 5.12.5->5.12 merges are done including qt5 and all submodules. 5.12->5.13 merges are still ongoing. —Liang > On 6 Sep 2019, at 14:19, Liang Qi wrote: > > Integrations > > * qt5 5.12 and 5.13 are healthy, the last submodule update integrated at 2 > days ago > * qt5 5.14: > * ongoing: https://codereview.qt-project.org/c/qt/qt5/+/272221 , hope > it could finish a bit later tonight > * previous integrated submodule update is 8 days ago. > * qt5 dev: > * previous integrated submodule update is 2 weeks ago. > * will try https://codereview.qt-project.org/c/qt/qt5/+/271472 again > after https://codereview.qt-project.org/c/qt/qtquickcontrols2/+/273065 > integrated, perhaps will happen during this weekend > * qt5 5.15, guess the situation is similar like dev, haven't tried yet > > Merges > > * 5.13.1->5.13 merges almosted finished except a few modules and qt5 > 5.13.1->5.13 > * plan to have qt5 5.12.5->5.12->5.13 merges during weekend > > Anyway, with current setup, 5.12/5.12.5/5.13/5.13.5/5.14/5.15/dev and there > are two branches which are in active developemnt, wip/qt6 and wip/cmake. Lots > of things related with merges are expected. Hope we can impove the situation > very soon. > > Nice weekend! > > Report from Liang > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Merge and Integration status report - 2019.09.06
Integrations * qt5 5.12 and 5.13 are healthy, the last submodule update integrated at 2 days ago * qt5 5.14: * ongoing: https://codereview.qt-project.org/c/qt/qt5/+/272221 , hope it could finish a bit later tonight * previous integrated submodule update is 8 days ago. * qt5 dev: * previous integrated submodule update is 2 weeks ago. * will try https://codereview.qt-project.org/c/qt/qt5/+/271472 again after https://codereview.qt-project.org/c/qt/qtquickcontrols2/+/273065 integrated, perhaps will happen during this weekend * qt5 5.15, guess the situation is similar like dev, haven't tried yet Merges * 5.13.1->5.13 merges almosted finished except a few modules and qt5 5.13.1->5.13 * plan to have qt5 5.12.5->5.12->5.13 merges during weekend Anyway, with current setup, 5.12/5.12.5/5.13/5.13.5/5.14/5.15/dev and there are two branches which are in active developemnt, wip/qt6 and wip/cmake. Lots of things related with merges are expected. Hope we can impove the situation very soon. Nice weekend! Report from Liang ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Merge and Integration status report - 2019.06.28
Integrations * qt5 5.12: submodule updated two days ago. The only issue is qtvirtualkeyboard was decoupled from qt5, see https://bugreports.qt.io/browse/QTBUG-76371 , need to wait COIN production update * qt5 5.13: submodule updated three days ago. The only issue is https://bugreports.qt.io/browse/QTBUG-76549 , tst_Dialogs failed on macOS 10.13 * qt5 dev: submodule updated this morning. qtwebengine is decoupled from qt5 because above QTBUG-76549. Merges * qt5 5.12.4->5.12 merges are done, all submodules and qt5 * qt5 5.13.0->5.13 merges are still on-going * and 5.12->5.13->dev will come, especially for qt5 Etc * In these last few days for the 1st half year of 2019, there are several tasks have more priority inside TQtC. So some cancellation of integrations happened for this purpose. Hope this doesn't hurt much. Enjoy summer(or winter)! --Liang ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Merge and Integration status report - 2019.05.09
Integrations and Provisionings * qt5 5.9, 5.12, 5.13, 5.13.0 and dev are healthy, after https://testresults.qt.io/coin/integration/qt/qt5/tasks/1557406940 , qt5 dev finally got integrated after about 4 weeks. Merges Please check https://codereview.qt-project.org/#/q/owner:%22Qt+Forward+Merge+Bot+%253Cqt_forward_merge_bot%2540qt-project.org%253E%22++status:open,n,z * Healthy, 5.12.3->5.12 merges are done --Liang ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Merge and Integration status report - 2019.03.15
Integrations and Provisionings * qt5 5.12, 5.13 and dev are healthy, finally after https://testresults.qt.io/coin/integration/qt/qt5/tasks/1552656661 Merges Please check https://codereview.qt-project.org/#/q/owner:%22Qt+Forward+Merge+Bot+%253Cqt_forward_merge_bot%2540qt-project.org%253E%22++status:open,n,z * Healthy, 5.12.2->5.12 merges are ongoing --Liang ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Merge and Integration status report - 2019.03.08
Integrations and Provisionings * qt5 5.12 and 5.13 are healthy * qt5 dev: submodule update on March 4 excluded qtbase, the previous one with qtbase in about one month ago on Feb. 7. Currently only known blocker is https://bugreports.qt.io/browse/QTBUG-74126 , Parse error at "ContactFieldType_Location" and Oliver Wolff has a fix at https://codereview.qt-project.org/#/c/254717/ . Merges Please check https://codereview.qt-project.org/#/q/owner:%22Qt+Forward+Merge+Bot+%253Cqt_forward_merge_bot%2540qt-project.org%253E%22++status:open,n,z * Need some help on qtdeclarative 5.12->5.13 https://codereview.qt-project.org/#/c/254450/ * qt5 5.13->dev merge depends on qt5 dev integrated with latest qtbase first, see https://codereview.qt-project.org/#/c/254215/ Happy International Women's Day! and nice weekend. --Liang ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Merge and Integration status report - 2019.02.01
Merges * Submodules and qt5 are fine. Integrations and Provisionings * qt5 5.12 are healthy * Trying to have a few changes from Ryan, about docker based network test server for Windows, see https://codereview.qt-project.org/#/q/status:open+project:qt/qt5+branch:dev+topic:%22docker-based+testserver%22,n,z , but failed, because https://bugreports.qt.io/browse/QTQAINFRA-2717 , The same agent called agentLaunched twice, that should not happen, forcefully restarting this workitem . And looks like it also blocks qtbase dev integrations. * qt5 dev is 3 days old, I think it is also affected by above issue. * qt5 5.13, haven't tried, because the final down merge dev->5.13 is not finished yet --Liang ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Merge and Integration status report - 2019.01.22
First issue on 2019! Generally, CI/COIN was in a very good mood after the new year update. Then we met https://bugreports.qt.io/browse/QTBUG-73116 , tst_QString::localeAwareCompare fails (dev) and a few other issues. Now it looks like most of them got fixed already. Merges * Submodules 5.12->dev merge are fine * qt5 5.12->dev merge is ongoing, see https://codereview.qt-project.org/#/c/249863/ , currently blocked by https://bugreports.qt.io/browse/QTQAINFRA-2591 , Windows 10 provisionigs stuck on sdkmanager, Tony is working on that, perhaps we need more Yes to those questions... Integrations * qt5 5.12.1/5.12 are healthy * qt5 dev is 5 days old, expected to have new round with qt5 5.12->dev merge after QTQAINFRA-2591 got fixed --Liang ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Merge and Integration status report - 2018.12.22
Thanks a lot Liang!! Simon > On 23. Dec 2018, at 00:11, Tor Arne Vestbø wrote: > > Happy new year Liang, excellent work! > > tor arne > >> On 22 Dec 2018, at 23:26, Liang Qi wrote: >> >> Merges >> >> * 5.11.3->5.11 merges are done, including qt5, so 5.11.3 branch could be >> nuked. >> * 5.12.0->5.12, qt5 one https://codereview.qt-project.org/#/c/248857/ is >> ongoing >> * 5.11->5.12, still missing qtwebengine and qt5 >> * 5.12->dev, need to be done after new year >> >> Integrations >> >> * 5.12 is healthy >> * dev got latest submodule update merged in >> https://codereview.qt-project.org/#/c/174522/ this morning. >> >> Happy new year! >> >> --Liang >> ___ >> Development mailing list >> Development@qt-project.org >> https://lists.qt-project.org/listinfo/development > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Merge and Integration status report - 2018.12.22
Happy new year Liang, excellent work! tor arne > On 22 Dec 2018, at 23:26, Liang Qi wrote: > > Merges > > * 5.11.3->5.11 merges are done, including qt5, so 5.11.3 branch could be > nuked. > * 5.12.0->5.12, qt5 one https://codereview.qt-project.org/#/c/248857/ is > ongoing > * 5.11->5.12, still missing qtwebengine and qt5 > * 5.12->dev, need to be done after new year > > Integrations > > * 5.12 is healthy > * dev got latest submodule update merged in > https://codereview.qt-project.org/#/c/174522/ this morning. > > Happy new year! > > --Liang > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Merge and Integration status report - 2018.12.22
Merges * 5.11.3->5.11 merges are done, including qt5, so 5.11.3 branch could be nuked. * 5.12.0->5.12, qt5 one https://codereview.qt-project.org/#/c/248857/ is ongoing * 5.11->5.12, still missing qtwebengine and qt5 * 5.12->dev, need to be done after new year Integrations * 5.12 is healthy * dev got latest submodule update merged in https://codereview.qt-project.org/#/c/174522/ this morning. Happy new year! --Liang ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Merge and Integration status report - 2018.11.15
Integrations * qt5 5.9/5.11/5.11.3/5.12/5.12.0 integrations are healthy * qt5 dev integrations: qtbase didn't update for about two weeks * https://bugreports.qt.io/browse/QTBUG-71804 'GLsizeiptr' and 'GLintptr': redefinition; different basic types, qtwebengine team is working on it Gerrit * qtbase 5.12 is still locked(others repos 5.12 got unlocked on Nov. 13 morning) -- Liang ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Merge and Integration status report - 2018.10.29
Integrations * qt5 5.9/5.11/5.12/dev integrations are healthy Merges * qtdeclarative 5.11->5.12 merge(10 days) is ongoing, https://codereview.qt-project.org/#/c/243050/ * qtbase 5.11->5.12 merge, need help, https://codereview.qt-project.org/#/c/243826/ * qtbase 5.12->dev merged on Saturday, https://codereview.qt-project.org/#/c/243500/ I will check other 5.11->5.12 merges today before the latest 5.12->5.12.0 final down merge. Provisionings * qt5 5.12: Android NDK(r18b) and SDK updated on all host platforms on Oct. 20 * qt5 dev: Trying to integrate https://codereview.qt-project.org/#/c/240554/ (Docker Provisioning: Install Docker-based test servers on macOS) soon -- Liang ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Merge and Integration status report - 2018.09.28
Integrations * qt5 5.9/5.11 integrations are healthy * qt5 5.12, one integration was done this morning, but qtbase was two days old. * * https://bugreports.qt.io/browse/QTBUG-70779 libqtgeoservices_mapboxgl.so link failure on android. Root cause was found, need help to find final solution. * qt5 dev, last integration was two weeks ago, will try a new one after qtwebengine 5.12->dev merge finished, see https://codereview.qt-project.org/#/c/241338/ , still need someone's +2. -- Liang ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Merge and Integration status report - 2018.09.05
Integrations * qt5 5.11/5.11.2/5.12 integrations are healthy, finally for 5.12 * qt5 dev, 5.12->dev merge + dev submodule update integration just started, let's see COIN is a bit slow recently, the difference between backend vm numbers and coin running numbers is a bit too much. Colleagues are working on that. During this period, perhaps qmake timeout issue is very common on all platforms, including Linux, Windows and macOS. -- Liang ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Merge and Integration status report - 2018.08.13
> -Original Message- > From: Development project.org> On Behalf Of Liang Qi > Sent: maanantai 13. elokuuta 2018 12.30 > To: development@qt-project.org > Subject: [Development] Merge and Integration status report - 2018.08.13 > > Integrations > > * qt5 5.11 integration is healthy, last one is yesterday, August 12 > > * qt5 dev, last one is August 11, excluding qtbase since August 8 > * * http://bugreports.qt.io/browse/QTBUG-69891 > tests/auto/quick/drawingmodes hanging > Tor Arne is working on that. But if can't get fix soon, suggest to revert > https://codereview.qt-project.org/#/c/235685/ for now, because there are > about 20-30 > changes including a 5.11->dev merge in qtbase which are not integrated in > qt5 dev yet. As discussed earlier we should do reverts much easier to avoid blocking of other's work. We will start branching from 'dev' -> '5.12' today and we should get latest changes in qtbase as soon as possible as well. So in my opinion we should just do the revert & bring the change back when fix is available. br, Jani > > Merges - healthy! > > Thanks Simon and Edward for their work during July! > > -- Liang > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Merge and Integration status report - 2018.08.13
Integrations * qt5 5.11 integration is healthy, last one is yesterday, August 12 * qt5 dev, last one is August 11, excluding qtbase since August 8 * * http://bugreports.qt.io/browse/QTBUG-69891 tests/auto/quick/drawingmodes hanging Tor Arne is working on that. But if can't get fix soon, suggest to revert https://codereview.qt-project.org/#/c/235685/ for now, because there are about 20-30 changes including a 5.11->dev merge in qtbase which are not integrated in qt5 dev yet. Merges - healthy! Thanks Simon and Edward for their work during July! -- Liang ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Merge and Integration status report - 2018.07.04
While Liang has been away (he'll be back later this week): Merges (various module owners; and I helped out a bit): * qt5's last upmerge was 5.11->dev on July 12 * qtbase 5.11->dev, https://codereview.qt-project.org/233803 took 20 tries, but we got there in the end (July 17); we've not had another integrate since, but one is in Coin as I write * four other modules merged yesterday. * we also got a 5.9->5.11 upmerge for qttranslations, today; that brought to light that 5.11 needed MODULE_VERSION updates in all modules. * 32 modules had 5.11->dev successful merges today (22 of them within an hour, 10:26 to 11:25), dealing with MODULE_VERSION conflicts * full history (and on-going activity) at: https://codereview.qt-project.org/#/q/owner:"Qt+Forward+Merge+Bot",n,z Integrations (Simon mostly): * qt5 dev, https://codereview.qt-project.org/233675 went through on July/18th followed by daily success all through last week but this week is blocked by QTBUG-69704, see https://codereview.qt-project.org/235389 * qt5 5.11 is healthy, also roughly daily, most recently today * full history (and on-going activity) at: https://codereview.qt-project.org/#/q/owner:"Qt+Submodule+Update+Bot",n,z Eddy. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Merge and Integration status report - 2018.07.04
Merges * qtbase 5.11->dev, https://codereview.qt-project.org/#/c/231959/ finally got merged after blocked about 3 weeks. A new round is ongoing, https://codereview.qt-project.org/#/c/233803/ Integrations * qt5 dev, last one is June 29, 4 days ago. A new one is at https://codereview.qt-project.org/#/c/233675/ , but wait for other provisioning changes. * * Issue: https://bugreports.qt.io/browse/QTBUG-69280 qtlocation: declarative_ui crash. Haven’t have time to check it yet. * qt5 5.11 is healthy, last one is yesterday During summer holiday, please help to keep an eye on merges at https://codereview.qt-project.org/#/q/owner:qt_forward_merge_bot%2540qt-project.org+status:open,n,z and integrations at https://codereview.qt-project.org/#/q/owner:qt_submodule_update_bot%2540qt-project.org+status:open,n,z . -- Liang ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Merge and Integration status report - 2018.07.01
Integrations * qt5 dev integration is healthy, last one is June 29 * qt5 5.11 integration is healthy finally again, last one is June 30 Merges * qtbase 5.11->dev is ongoing, https://codereview.qt-project.org/#/c/231959/ , which was blocked about 3 weeks, lots of changes from 5.11. I really want to have this merged as soon as possible. Looks like there is some issue with coin, need someone's help to check, perhaps reboot is needed. -- Liang ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Merge and Integration status report
Yes, declarative is open again. Simon From: Development on behalf of Tomasz Olszak Sent: Monday, June 25, 2018 11:12:30 AM To: development@qt-project.org Subject: Re: [Development] Merge and Integration status report Do you announce here once qtdeclarative ci is fixed and one can merge patch to staging? wt., 19 cze 2018 o 18:41 Ulf Hermann napisał(a): > > Hi, > > > 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. > > Nope, that didn't work. The slowdown lasts less than 15 minutes, but long > enough to trigger a timeout in the debugging tests after it goes away. So, we > don't get the watchdog to kill the tests (which would show the concurrently > running processes), but the tests still fail. See > https://bugreports.qt.io/browse/QTBUG-68741 for details. We either got > incredibly lucky with https://codereview.qt-project.org/231618 or the CI has > another bug and accepted this test although it shouldn't. > > br, > Ulf > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Merge and Integration status report
Do you announce here once qtdeclarative ci is fixed and one can merge patch to staging? wt., 19 cze 2018 o 18:41 Ulf Hermann napisał(a): > > Hi, > > > 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. > > Nope, that didn't work. The slowdown lasts less than 15 minutes, but long > enough to trigger a timeout in the debugging tests after it goes away. So, we > don't get the watchdog to kill the tests (which would show the concurrently > running processes), but the tests still fail. See > https://bugreports.qt.io/browse/QTBUG-68741 for details. We either got > incredibly lucky with https://codereview.qt-project.org/231618 or the CI has > another bug and accepted this test although it shouldn't. > > br, > Ulf > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Merge and Integration status report
Integrations * qt5 dev integration is healthy, last one is yesterday * qt5 5.11 integration failed from June 9, last integration was done on June 22, but skipped qtbase and qtwayland. * * Issue: [QTBUG-68773][1] 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. Suggest to revert to get 5.11 integrated again, [see the revert][2] Merges * qtbase 5.11->dev, the merge is blocked because [QTBUG-68773][1] is not fixed yet. -- Liang [1]: https://bugreports.qt.io/browse/QTBUG-68773 [2]: https://codereview.qt-project.org/#/c/233198/ ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Merge and Integration status report
Integrations * qt5 dev integration failed from June 18 * * Issue: [QTBUG-68848][1] tst_QQmlDebugJS fails too often in CI, perhaps a duplicate of [QTBUG-68741][2], the issue is there about two weeks, more talks in [previous report][4] * qt5 5.11 integration failed from June 9 * * Issue: [QTBUG-68773][3] 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. Suggest to revert to get 5.11 integrated again. Merges * qtbase 5.11->dev, the merge is blocked because [QTBUG-68773][3] is not fixed yet. -- Liang [1]: https://bugreports.qt.io/browse/QTBUG-68666 [2]: https://bugreports.qt.io/browse/QTBUG-68741 [3]: https://bugreports.qt.io/browse/QTBUG-68773 [4]: http://lists.qt-project.org/pipermail/development/2018-June/032893.html ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Merge and Integration status report
Hi, > 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. Nope, that didn't work. The slowdown lasts less than 15 minutes, but long enough to trigger a timeout in the debugging tests after it goes away. So, we don't get the watchdog to kill the tests (which would show the concurrently running processes), but the tests still fail. See https://bugreports.qt.io/browse/QTBUG-68741 for details. We either got incredibly lucky with https://codereview.qt-project.org/231618 or the CI has another bug and accepted this test although it shouldn't. br, Ulf ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Merge and Integration status report
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 Sent: Saturday, June 16, 2018 12:59:46 PM To: Simon Hausmann Cc: Jani Heikkinen; development@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 mailto:simon.hausm...@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 mailto:simon.hausm...@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@qt-project.org<mailto:development@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 mailto:development-bounces+jani.heikkinen=qt...@qt-project.org>> on behalf of Simon Hausmann mailto:simon.hausm...@qt.io>> Sent: Thursday, June 14, 2018 10:32 AM To: development@qt-project.org<mailto:development@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 mailto:development-bounces+simon.hausmann=qt...@qt-project.org>> on behalf of Liang Qi mailto:liang...@qt.io>> Sent: Thursday, June 14, 2018 9:18:32 AM To: development@qt-project.org<mailto:development@qt-project.org> Subject: [Development] Merge and Integration status repor
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 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 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@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 > on behalf of Simon Hausmann > Sent: Thursday, June 14, 2018 10:32 AM > To: development@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 > on behalf of Liang Qi > Sent: Thursday, June 14, 2018 9:18:32 AM > To: development@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 >
Re: [Development] Merge and Integration status report
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 mailto:simon.hausm...@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@qt-project.org<mailto:development@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 mailto:development-bounces+jani.heikkinen=qt...@qt-project.org>> on behalf of Simon Hausmann mailto:simon.hausm...@qt.io>> Sent: Thursday, June 14, 2018 10:32 AM To: development@qt-project.org<mailto:development@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 mailto:development-bounces+simon.hausmann=qt...@qt-project.org>> on behalf of Liang Qi mailto:liang...@qt.io>> Sent: Thursday, June 14, 2018 9:18:32 AM To: development@qt-project.org<mailto:development@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@qt-project.org<mailto:Development@qt-project.org> http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Merge and Integration status report
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@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 on behalf of Simon Hausmann Sent: Thursday, June 14, 2018 10:32 AM To: development@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 on behalf of Liang Qi Sent: Thursday, June 14, 2018 9:18:32 AM To: development@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@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] 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 on behalf of Simon Hausmann Sent: Thursday, June 14, 2018 10:32 AM To: development@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 on behalf of Liang Qi Sent: Thursday, June 14, 2018 9:18:32 AM To: development@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@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
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 on behalf of Liang Qi Sent: Thursday, June 14, 2018 9:18:32 AM To: development@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@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[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@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
