[Development] Blacklisting: CI vs non-CI

Simon Hausmann Simon.Hausmann at qt.io
Fri May 26 17:48:59 CEST 2017


Is it possible that you're looking for the "ci" keyword in the exclusion files?

Tor Arne implemented it for https://bugreports.qt.io/browse/QTBUG-59564


From: Development <development-bounces+simon.hausmann=qt.io at qt-project.org> on behalf of Thiago Macieira <thiago.macieira at intel.com>
Sent: Friday, May 26, 2017 8:45:28 AM
To: development at qt-project.org
Subject: [Development] Blacklisting: CI vs non-CI

I've seen some blacklists, in the past, that were real flaky tests: things that
would be unstable on any machine, given the proper conditions.

But most of the recent blacklists, and certainly all the BPASS I see when I
run tests, are due to the tests being run in an environment that runs 300x
slower than normal. Can we invent a blacklist that only applies to slow

I don't need to see those BPASS on 100% of the time that the test is run on my

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

Development mailing list
Development at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20170526/2f41f484/attachment.html>

More information about the Development mailing list