aboutsummaryrefslogtreecommitdiffstats
path: root/tests/auto/qml/debugger/qqmlinspector/BLACKLIST
diff options
context:
space:
mode:
authorSimon Hausmann <simon.hausmann@qt.io>2017-07-27 09:44:58 +0200
committerSimon Hausmann <simon.hausmann@qt.io>2017-07-28 13:35:46 +0000
commit80e03bbd9a42401d50af450aff5351c3a0c95444 (patch)
tree7c39e71f4f9fd5ca74003860b2645a917707b45c /tests/auto/qml/debugger/qqmlinspector/BLACKLIST
parent50bc2ac834502b2051dccaaec22da010a3ef5e70 (diff)
Ignore debugger failures with GCC on Windows
Capturing the output of the started process mysteriously fails on Windows with gcc. While the nested event loop is run, the readyRead() signal is never emitted. Only after the timer fired and the event loop is terminated, we receive the output we were expecting. Some tests needed adapting to the initializing sub-function failing in QVERIFY/QCOMPARE calls, in order for the process to not crash and the blacklisting to work. Task-number: QTQAINFRA-1334 Change-Id: I4804d94580e7db65595137d19d7b75d75c243257 Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@qt.io>
Diffstat (limited to 'tests/auto/qml/debugger/qqmlinspector/BLACKLIST')
-rw-r--r--tests/auto/qml/debugger/qqmlinspector/BLACKLIST2
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/auto/qml/debugger/qqmlinspector/BLACKLIST b/tests/auto/qml/debugger/qqmlinspector/BLACKLIST
new file mode 100644
index 0000000000..5fb1dc193b
--- /dev/null
+++ b/tests/auto/qml/debugger/qqmlinspector/BLACKLIST
@@ -0,0 +1,2 @@
+# QTQAINFRA-1334
+windows gcc