summaryrefslogtreecommitdiffstats
path: root/tests/auto/network/socket/qtcpsocket/BLACKLIST
diff options
context:
space:
mode:
authorTimur Pocheptsov <timur.pocheptsov@qt.io>2020-11-16 19:23:53 +0100
committerTimur Pocheptsov <timur.pocheptsov@qt.io>2020-11-20 14:34:04 +0100
commit4111d8e8e789c815ae37eb9903b042124e169078 (patch)
tree292ebf0eca8309853ccf83d008da4d1bdb8d6c0a /tests/auto/network/socket/qtcpsocket/BLACKLIST
parent289f909621a8d83320d33e3ff7d651c164034098 (diff)
tst_QTcpSocket::connectToHostError - handle possible timeouts
... instead of failing the test. On Ubuntu 20.04 when calling 'connect' with 0.0.0.1 we get EINPROGRESS and nothing else, since our own internal timer has 30 s. timeout, the event loop in the test stops before this and no socket error detected yet. Handle such situation without failing a test. Fixes: QTBUG-88042 Change-Id: Id6add27fcf9bbbe5fbf83a193652edf08fbad8d6 Reviewed-by: MÃ¥rten Nordheim <marten.nordheim@qt.io>
Diffstat (limited to 'tests/auto/network/socket/qtcpsocket/BLACKLIST')
-rw-r--r--tests/auto/network/socket/qtcpsocket/BLACKLIST1
1 files changed, 0 insertions, 1 deletions
diff --git a/tests/auto/network/socket/qtcpsocket/BLACKLIST b/tests/auto/network/socket/qtcpsocket/BLACKLIST
index 95e3e63977..ac243c0203 100644
--- a/tests/auto/network/socket/qtcpsocket/BLACKLIST
+++ b/tests/auto/network/socket/qtcpsocket/BLACKLIST
@@ -2,7 +2,6 @@
windows
[connectToHostError]
windows-10 gcc developer-build
-ubuntu-20.04
# QTBUG-66247
[delayedClose:WithSocks5Proxy]
windows-10 gcc developer-build