diff options
author | Timur Pocheptsov <timur.pocheptsov@qt.io> | 2017-11-07 11:51:57 +0100 |
---|---|---|
committer | Timur Pocheptsov <timur.pocheptsov@qt.io> | 2017-11-08 13:28:51 +0000 |
commit | 39355daa40438eef386ce55f02e7ba9ff824993f (patch) | |
tree | e43410ba0aa256bdf8f8dee24d3afff89ef2ccbf /config.tests/win/angle_d3d11_qdtd | |
parent | fad8f340333f1c9ec7b6cebe521d53f4b1da4f8d (diff) |
tst_QNetworkReply::getFromUnreachableIp - fix a failing test
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>
Diffstat (limited to 'config.tests/win/angle_d3d11_qdtd')
0 files changed, 0 insertions, 0 deletions