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.
So a few builds later:
Without the patch, success: /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
https:/
With the patch again, fail: /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
https:/
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.