13.10
*To: *Simon Hausmann ,
"development@qt-project.org"
*Subject: *Re: [Development] COIN failures on dev
Ah, so last successful integration on qt5 super module was nearly a
month ago?? 11/172017
Now, what I was really after was last generally unsuccessful
integration to see h
ongoing to unblock it.
Yours,
Tuukka
From: Development on
behalf of Adam Treat
Date: Tuesday, 12 December 2017 at 13.10
To: Simon Hausmann , "development@qt-project.org"
Subject: Re: [Development] COIN failures on dev
Ah, so last successful integrat
?
From: Simon Hausmann
Sent: Tuesday, December 12, 2017 3:09:03 AM
To: Adam Treat; development@qt-project.org
Subject: Re: [Development] COIN failures on dev
Hi,
I find the easiest way to find the last successful integration for example for
qt5.git dev is this
on
behalf of Adam Treat
Sent: Monday, December 11, 2017 5:47:41 PM
To: development@qt-project.org
Subject: Re: [Development] COIN failures on dev
Whenever I discover something seemingly broken in an area of code I'm
unfamiliar with I first suspect I don't understand something...
Righ
On Monday, 11 December 2017 08:47:41 PST Adam Treat wrote:
> Whenever I discover something seemingly broken in an area of code I'm
> unfamiliar with I first suspect I don't understand something...
>
> Right now I'm looking for the last successful dev branch integration on
> qt5 supermodule and I c
Whenever I discover something seemingly broken in an area of code I'm
unfamiliar with I first suspect I don't understand something...
Right now I'm looking for the last successful dev branch integration on
qt5 supermodule and I can not find it. I've gone back to before
Thanksgiving.
Can this
Hi,
For the past few business days we've all witnessed failures on dev
branch like this: https://codereview.qt-project.org/#/c/213309/
Seems that something broke with provisioning on macOS or something. I
see this https://codereview.qt-project.org/#/c/214045/ attempt to fix,
but that is also
