[Development] Flaky auto tests on macOS 10.12

Tony Sarajärvi tony.sarajarvi at qt.io
Mon Jun 19 13:09:31 CEST 2017

It is the intention that we do this. But we're constantly running, not beside our horse, but after it. We have just begun activating ourselves to discuss about 5.10 platforms and we have FF coming up in two weeks (counting out July here).
It took months to blacklist all the cases for 10.12 alone. So yes, I agree that how we do this is not good, but at some point we find it good enough. I ran qt5 builds through twice without failures and deemed it fit. Before that I kept blacklisting everything I saw (which actually isn't good either).

Dev branch is actually the place where they should be put yes. Unfortunately we are too late for that. We need 10.12 in 5.9, and for it to still be in dev branch, we should have put it in January. We were still working with our 5.8 platforms at that time. As I said...the horse is running away from us 😉


-----Original Message-----
From: Development [mailto:development-bounces+tony.sarajarvi=qt.io at qt-project.org] On Behalf Of Morten Sørvig
Sent: maanantai 19. kesäkuuta 2017 13.40
To: development at qt-project.org
Subject: Re: [Development] Flaky auto tests on macOS 10.12

> On 19 Jun 2017, at 08:34, J-P Nurmi <jpnurmi at qt.io> wrote:
> [*] The timing, during the 5.9.1 soft freeze week, was a bit unfortunate, but this is a separate discussion.

Introducing a new configuration to the CI system should be considered a development task, subject to the usual branch policies. Can we establish that this happens in dev first, ideally before the feature freeze?


Development mailing list
Development at qt-project.org

More information about the Development mailing list