diff options
author | Timur Pocheptsov <timur.pocheptsov@qt.io> | 2018-11-07 12:48:29 +0100 |
---|---|---|
committer | Timur Pocheptsov <timur.pocheptsov@qt.io> | 2018-11-07 12:25:12 +0000 |
commit | d786c55b9e03c3cb8444ebeef8d31ca9d84071a0 (patch) | |
tree | 642b1502ba84b2fc5dd232c02f9a6ddea779a214 /tests/auto/cmake/test_qtmainwin_library | |
parent | edacfd2f0b6f95430b62296853c3ae5b3405b406 (diff) |
Make tst_qsslsocket::protocolServerSide() less flaky
By accident, when we erroneously tried testing TlsV1_3 on macOS with
SecureTransport (which does not support TLS 1.3) we hit this quite
subtle problem: it can happen that a server-side socket is never
created but a client (after TCP connection was established) fails
in TLS initialization and ... stops the loop preventing
SslServer::incomingConnection() from creating its socket. Then we
dereference nullptr.
Task-number: QTBUG-71638
Change-Id: I8dc5a4c53022a25aafe2c80a6931087517a48441
Reviewed-by: MÃ¥rten Nordheim <marten.nordheim@qt.io>
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
Diffstat (limited to 'tests/auto/cmake/test_qtmainwin_library')
0 files changed, 0 insertions, 0 deletions