Hi Rich, We should move the tests to use qt.io certificate. We will eventually get qt-project.org certificate, but it is still better to use qt.io for the tests.
For a short term solution, perhaps we could simply disable failing SSL tests and get them back when we have changed these for qt.io Yours, Tuukka From: Richard Moore <[email protected]<mailto:[email protected]>> Date: Monday 26 January 2015 23:34 To: Marc Mutz <[email protected]<mailto:[email protected]>> Cc: Qt Project Development Mailing-List <[email protected]<mailto:[email protected]>> Subject: Re: [Development] Certificate expires soon, new one ordered Sigh. It looks like some of the tests are using qt-project.org<http://qt-project.org> even though they aren't supposed to: void tst_QSslSocket_onDemandCertificates_member::onDemandRootCertLoadingMemberMethods() { QString host("qt-project.org<http://qt-project.org>"); // not using any root certs -> should not work QSslSocketPtr socket2 = newSocket(); this->socket = socket2.data(); socket2->setCaCertificates(QList<QSslCertificate>()); socket2->connectToHostEncrypted(host, 443); QVERIFY(!socket2->waitForEncrypted()); Grr. Rich. On 26 January 2015 at 20:54, Richard Moore <[email protected]<mailto:[email protected]>> wrote: On 26 January 2015 at 19:28, Marc Mutz <[email protected]<mailto:[email protected]>> wrote: I guess that's the reason why no integration succeeds in qtbase atm (always some ssl test error)? If so, it might be a good idea to suspend qtbase integration tasks until it's fixed, unless people like to have it running as a compilation oracle... The network test server doesn't depend on the qt-project cert. Rich.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
