The test quite often locks up (even reproduceable on local machine):
gent:2019/06/03 05:21:44 build.go:197: QFATAL : tst_QNetworkReply::ioPostToHttpsUploadProgress() Test function timed out
agent:2019/06/03 05:21:44 build.go:197: FAIL! : tst_QNetworkReply::ioPostToHttpsUploadProgress() Received a fatal error.
agent:2019/06/03 05:21:44 build.go:197: Unknown file(0) : failure location
agent:2019/06/03 05:21:44 build.go:197: Totals: 385 passed, 1 failed, 21 skipped, 94 blacklisted, 580942ms
agent:2019/06/03 05:21:44 build.go:197: ********* Finished testing of tst_QNetworkReply *********
My naive analysis:
at tests/auto/network/access/qnetworkreply/tst_qnetworkreply.cpp:5045 the SslServer is started . Further down, QNetworkReply is started, which immediately fires some SSL errors (host does not have certificate, etc etc). This locks up with the server accessing the global SSL error list (see stack trace). With the diagnostic patch, this happens after step "l4".