Some qtpim tests start failing when built against Qt 5.3.2
Bug #1376644 reported by
Timo Jyrinki
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qtpim-opensource-src (Ubuntu) |
New
|
High
|
Renato Araujo Oliveira Filho |
Bug Description
Update: the bug is that tests fail if the build and test run is not done inside the source tree
Some qtpim tests start failing when built against Qt 5.3.2:
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:/
tags: | added: qt5.3 |
description: | updated |
description: | updated |
description: | updated |
To post a comment you must log in.
Update:
I've moved the new qtpim snapshot to https:/ /launchpad. net/~canonical- qt5-edgers/ +archive/ qt5-daily - you can enable that PPA in addition to the 5.3.2 PPA to use it, or you can just get the sources from there.
The reason is that that new snapshot would also change a symbol requiring a telephony-service rebuild (at least), and the rebuild fails because a unit test starts failing.
So I'd rather see the original problem fixed, ie rebuilding the current qtpim as is has test failures. The newest such build is now at https:/ /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ landing- 015/+sourcepub/ 4485840/ +listing- archive- extra - I'll follow that with a build where running the tests is disabled (commenting out one line in debian/rules) so that there's something that can be used for testing the whole PPA.