Mårten Nordheim fc9ae22c88 tst_qsslsocket: fix racy test ... In this threaded setup the server can sometimes have the data before it calls "waitForReadyRead", what happens then is that we fail the wait and as a result the test fails overall. Let's check if we actually got some data after all and then continue if we did. Since both the client and the server currently wait the same amount of time (2s) the max timeout for the client was increased by 0.5s so it has some time to notice that the server got the message. Change-Id: Ib5915958853413047aa5a7574712585bcae28f79 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io> Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> (cherry picked from commit e79b1dcdf5) Reviewed-by: Simo Fält <simo.falt@qt.io> (cherry picked from commit d53b8b77bc) Change-Id: I2f6ffb8e0a9b4d591edb6925e48baffcefc14511 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>		2019-06-13 04:18:18 +00:00
..
access	H2 auto-test, degrage flowControlServerSide	2019-06-13 04:16:54 +00:00
bearer	Add cmdline feature to qmake	2019-02-18 07:12:14 +00:00
kernel	Populate test data for reverse lookups using system tools	2019-04-05 05:50:18 +00:00
socket	Make tst_QUdpSocket::lincLocalIPv6 less sadistic	2019-02-21 11:14:48 +00:00
ssl	tst_qsslsocket: fix racy test	2019-06-13 04:18:18 +00:00
network.pro	Re-enable network tests on Mac OS.	2012-04-24 16:06:28 +02:00