39355daa40
This patch works around Windows X86 on QEMU antics. It appears on this platform the test behaves in some unpredictable manner: - WSAConnect with 255.255.255.255 does not always immediately fail with some error, so socket engine waits for a connection timeout (30 s.), but the test itself - only waits for 5 seconds and then tests that a request has finished with error, which is not true (we are still connecting). To make it work - whenever we have bearermanager feature enabled, set a connection timeout to something reasonable, not 30 s. Since we try to connect to each address twice, make timeout 1.5 s (so it's 3 s. in total and still is < 5 s.). Task-number: QTBUG-64264 Change-Id: I1d40c140667fca8402ec9344e66d313b6df54256 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> |
||
---|---|---|
.. | ||
hpack | ||
hsts | ||
http2 | ||
qabstractnetworkcache | ||
qftp | ||
qhttpnetworkconnection | ||
qhttpnetworkreply | ||
qnetworkaccessmanager | ||
qnetworkcachemetadata | ||
qnetworkcookie | ||
qnetworkcookiejar | ||
qnetworkdiskcache | ||
qnetworkreply | ||
qnetworkrequest | ||
spdy | ||
access.pro |