Details
-
Bug
-
Resolution: Unresolved
-
P1: Critical
-
None
-
6.8
-
None
-
macOS
-
a553650ef (dev), 4482206a0 (dev), 3152d20ba (dev), c2c187357 (dev), bbcdd53d9 (6.8), fbfc0ab8d (dev), 0113690d8 (6.8), 2a3610d77 (dev), eecc0ad04 (6.8), 57eabffbc (dev), 076f89744 (6.8), 81e7d3f95 (dev), 350279055 (6.8), c9d1f18d0 (dev), 1c90c7ce0 (dev)
Description
All of these seem to fail due to SSL issues:
- tst_qwebengineclientcertificatestore::clientAuthentication
- tst_qwebsocket::authenticationRequired
- tst_qnetworkreply
While this one seems to perhaps be something else
- tst_qhttpserver::pipelinedRequests
- tst_qhttpservermultithreaded (several tests)
- tst_qabstracthttpserver::verifyWebSocketUpgrades
Also, after fixing several auto-tests in different modules we can see the proliferation of the code that checks if keychain access would block auto-test. Makes sense to implement this instead as a part of the test-lib.