So a few builds later: Without the patch, success: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-022/+build/6569022/+files/buildlog_ubuntu-rtm-14.09-amd64.qtbase-opensource-src_5.3.0%2Bdfsg-2ubuntu10%7Eutopic1%7Etest10_UPLOADING.txt.gz
With the patch again, fail: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-022/+build/6569183/+files/buildlog_ubuntu-rtm-14.09-amd64.qtbase-opensource-src_5.3.0%2Bdfsg-2ubuntu10%7Eutopic1%7Etest11_FAILEDTOBUILD.txt.gz Any ideas what could cause the unit test to reliably fail with the patch added, given that the patch only touches bearer code and the failure is in tst_QXmlStream? There is the option to start disabling additional unit tests, but QA probably would not accept that without understanding the cause for failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
