AuroraMiddleware/qt5base-lts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Blacklist tst_QGuiEventLoop::processEvents on QNX

Browse Source 
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>
This commit is contained in:
Volker Hilsheimer 2023-11-22 15:13:20 +01:00
parent 18aa36cf87
commit d2c6e9ab99
2 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tests/auto/corelib/kernel/qeventloop/BLACKLIST Normal file
View File

@ -0,0 +1,2 @@
[processEvents:gui]
qnx # QTBUG-119359

14
tests/auto/corelib/kernel/qeventloop/tst_qeventloop.cpp
View File

@ -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);