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 integrat
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:
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/br
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+
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++st
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_Lo
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+testse
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->
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
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, sti
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
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
Gerr
Integrations
* qt5 5.9/5.11 integrations are healthy
* qt5 5.12/dev integrations: skipped qtbase after
https://codereview.qt-project.org/#/c/243906/ .
* Issue: https://bugreports.qt.io/browse/QTBUG-71550 , a fix at
https://codereview.qt-project.org/#/c/244725/ , but didn't get integrated
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,
h
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
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
> -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.1
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, sugg
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 anoth
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-projec
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 wan
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
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
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
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-6
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
o 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?
> 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: develop
imon.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 ch
roject.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 th
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 stag
evelopment@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::MappingManagerE
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 workin
33 matches
Mail list logo
