91ab70d17f
We use global object to store errors found by q_X509Callback. Thus, we also use a lock/mutex. It would appear all tests involving in-process server and QNAM are prone to intermittent failures on our Windows VMs - it's always about timeouts due to the client socket (QNAM) locking and the server socket blocking main thread while trying to acquire the same lock. The real fix is to get rid of global variable/locking, we'll have it later (quite a change and requires a lot of accuracy). Task-number: QTBUG-76247 Change-Id: Iffc90d9e16783f17f62e836e01c35f22681bdd39 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> |
||
|---|---|---|
| .. | ||
| certs | ||
| echo | ||
| test | ||
| .gitattributes | ||
| .gitignore | ||
| BLACKLIST | ||
| bigfile | ||
| element.xml | ||
| empty | ||
| image1.jpg | ||
| image2.jpg | ||
| image3.jpg | ||
| index.html | ||
| qnetworkreply.pro | ||
| qnetworkreply.qrc | ||
| resource | ||
| rfc3252.txt | ||
| smb-file.txt | ||
| testserver_index.html | ||
| tst_qnetworkreply.cpp | ||
