Comment 22 for bug 1470700

FAIL! : tst_QXmlInputSource::waitForReadyIODevice() 'reply->error() == QNetworkReply::NoError' returned FALSE. ()
   Loc: [tst_qxmlinputsource.cpp(150)]

This test is http client/server test. I have tested this here and it hangs on previous version (5.4.2) as well. The request never gets the finished signal.

As for the attachment in #20, it also fails at:

FAIL! : tst_QUdpSocket::initTestCase() 'networkSession->waitForOpened(30000)' returned FALSE. ()
   Loc: [../tst_qudpsocket.cpp(179)]

In which case is a test that fails to check for start/stop capabilities before it tries to open a NetworkSession (which will fail using only the generic bearer plugin (like a system without networkmanager or connman), as it cannot start or stop interfaces/connections like the network manager bearer plugin can.

Not knowing all that much about ubuntu tests, looking at that weather app log:
(but I do know app armor blocks QNAM/network manager dbus requests, and I believe they refuse to open app armor to allow clients to access QNAM/network manager)

QNetworkManagerInterface::QNetworkManagerInterface(QObject*) propsReply "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.117" (uid=32011 pid=4194 comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ u") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1440 comm="NetworkManager ")"
QNetworkManagerInterface::QNetworkManagerInterface(QObject*) nmReply "An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.117" (uid=32011 pid=4194 comm="/usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ u") interface="org.freedesktop.NetworkManager" member="GetDevices" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1440 comm="NetworkManager ")"