Mårten Nordheim 27f52942b4 tst_QTcpSocket: stabilize connectToHostError ... It's not _wrong_ to time out when connecting to something unreachable (it's just a different way of handling it) so we shouldn't fail when this happens either. In local testing (windows) it times out after 8 seconds, so bump the timer to 10 seconds. On systems where it's faster there'll be no difference as long as things don't go wrong. Pick-to: 6.0 Fixes: QTBUG-89089 Change-Id: I8437cf8e4fbecedea2391ed87fdce1213085b964 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>		2020-12-04 00:17:46 +01:00
..
stressTest	Another round of replacing 0 with nullptr	2020-10-07 23:02:47 +02:00
test	CMake: Regenerate projects to use new qt_internal_ API	2020-09-23 16:59:06 +02:00
.gitignore	Moved network autotests into new directory structure	2011-09-09 09:32:17 +02:00
BLACKLIST	tst_QTcpSocket::connectToHostError - handle possible timeouts	2020-11-20 14:34:04 +01:00
CMakeLists.txt	CMake: Regenerate and fix qtcpsocket test	2020-03-18 16:36:26 +01:00
qtcpsocket.pro	tst_QTcpSocket::suddenRemoteDisconnect - fix flakyness	2017-10-30 11:10:10 +00:00
tst_qtcpsocket.cpp	tst_QTcpSocket: stabilize connectToHostError	2020-12-04 00:17:46 +01:00