Blacklist tst_QGuiEventLoop::processEvents on QNX

The test log shows flaky failures of this test several times a day on
QNX, so blacklist it.
To do that, we need to be able to isolate the "GUI" mode of this test.
To do that, add a single data tag that depends on whether the test
project is built for GUI or Core, and blacklist only the "gui" data tag.

Task-number: QTBUG-119359
Pick-to: 6.6
Change-Id: I91c2380de0a3febedcf781f27fed4a1fa6aa5515
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

1 files changed, 14 insertions, 0 deletions

diff --git a/tests/auto/corelib/kernel/qeventloop/tst_qeventloop.cpp b/tests/auto/corelib/kernel/qeventloop/tst_qeventloop.cpp
index 4ebeec6083..442750aee4 100644
--- a/tests/auto/corelib/kernel/qeventloop/tst_qeventloop.cpp
+++ b/tests/auto/corelib/kernel/qeventloop/tst_qeventloop.cpp
@@ -140,6 +140,7 @@ class tst_QEventLoop : public QObject
     Q_OBJECT
 private slots:
     // This test *must* run first. See the definition for why.
+    void processEvents_data();
     void processEvents();
     void exec();
     void reexec();
@@ -161,8 +162,21 @@ protected:
     void customEvent(QEvent *e) override;
 };
 
+void tst_QEventLoop::processEvents_data()
+{
+    QTest::addColumn<QString>("mode");
+
+#ifdef QT_GUI_LIB
+    QTest::addRow("gui") << "gui";
+#else
+    QTest::addRow("core") << "core";
+#endif
+}
+
 void tst_QEventLoop::processEvents()
 {
+    QFETCH(QString, mode);
+
     QSignalSpy aboutToBlockSpy(QAbstractEventDispatcher::instance(), &QAbstractEventDispatcher::aboutToBlock);
     QSignalSpy awakeSpy(QAbstractEventDispatcher::instance(), &QAbstractEventDispatcher::awake);