Renato's analysis was at the end that it works locally, if just the qtpim packages are installed system wide before running the tests. This is a change in behavior from when qtpim was built against Qt 5.3.0, where such a requirement did not exist.
This bug should remain open as the core issue should be fixed, but as tests pass locally it could be ok to temporarily disable those additional tests in qtpim. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1376644 Title: Some qtpim tests start failing when built against Qt 5.3.2 Status in “qtpim-opensource-src” package in Ubuntu: New Bug description: Some qtpim tests start failing when built against Qt 5.3.2: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-015/+sourcepub/4451482/+listing- archive-extra We shouldn't be disabling additional tests, so the root causes should be found. All seem to have the following thing in common: "ASSERT failure in QTest::fetchData(): "Test data requested, but no testdata available.", file qtestcase.cpp, line 2047" You can test the Qt 5.3.2 yourself by following the instructions at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtpim-opensource-src/+bug/1376644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
