tst_QSslSocket::readBufferMaxSize() - workaround the flaky test

Task-number: QTBUG-94186
Change-Id: I8c82f1fede8f9512f531f4ff17508b9e71ebf0b7
Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>

1 files changed, 12 insertions, 0 deletions

diff --git a/tests/auto/network/ssl/qsslsocket/tst_qsslsocket.cpp b/tests/auto/network/ssl/qsslsocket/tst_qsslsocket.cpp
index 7e93f2dde6..d3d0110288 100644
--- a/tests/auto/network/ssl/qsslsocket/tst_qsslsocket.cpp
+++ b/tests/auto/network/ssl/qsslsocket/tst_qsslsocket.cpp
@@ -3647,6 +3647,18 @@ void tst_QSslSocket::verifyClientCertificate()
 
 void tst_QSslSocket::readBufferMaxSize()
 {
+    // QTBUG-94186: originally, only SecureTransport was
+    // running this test (since it was a bug in that backend,
+    // see comment below), after TLS plugins were introduced,
+    // we enabled this test on all backends, as a part of
+    // the clean up. This revealed the fact that this test
+    // is flaky, and it started to fail on Windows.
+    // TODO: this is a temporary solution, to be removed
+    // as soon as 94186 fixed for good.
+    if (!isTestingSecureTransport)
+        QSKIP("This test is flaky with TLS backend other than SecureTransport");
+
+
     // QTBUG-55170:
     // SecureTransport back-end was ignoring read-buffer
     // size limit, resulting (potentially) in a constantly