Hi again The CI seemed to suffer from the same problem as our personal instances of the CI did: hardware was not allocated per request, nor did cleaning up of VMs work. So my best bet is that something went bad on vSphere's side. What exactly, we don't know, but a restart of the CI seemed to do the trick.
So stage ahead :) -Tony From: Development [mailto:development-bounces+tony.sarajarvi=qt...@qt-project.org] On Behalf Of Tony Sarajärvi Sent: 22. marraskuuta 2016 9:12 To: development@qt-project.org Subject: [Development] CI suffering from an unknown problem Hi There's something off in the CI currently and we're investigating. -Tony Tony Sarajärvi CI Tech Lead The Qt Company Elektroniikkatie 10 90590, Oulu Finland tony.saraja...@qt.io<mailto:tony.saraja...@qt.io> +358 50 4821416 http://qt.io<http://qt.io/> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/qt_logo_with_text_green_rgb_400x141.png]<http://qt.io/> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_twitter.png]<http://www.twitter.com/qtproject> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_linkedin.png]<https://www.linkedin.com/company/the-qt-company/> [http://s3-eu-west-1.amazonaws.com/qt-files/logos/SoMe/qt_youtube.png]<https://www.youtube.com/QtStudios>
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
