Fwd: Unittests: kcalendartest.cpp
Jon Severinsson
jon at severinsson.net
Fri Dec 14 17:23:23 UTC 2012
At Friday 14 December 2012 15:07:26 David Faure wrote:
> The fix for all the kio-related tests is to
> export QT_PLUGIN_PATH=$PREFIX/lib/plugins
> (or lib64 if you're using that)
Thanks, that helps, but unfortunately it isn't enough :(
88% tests passed, 14 tests failed out of 120
Total Test time (real) = 78.92 sec
The following tests FAILED:
4 - kdecore-kmountpointtest (Failed)
8 - kdecore-kshelltest (Failed)
11 - kdecore-kdatetimetest (Failed)
18 - kdecore-ktcpsockettest (Failed)
22 - kdecore-kcalendartest (Failed)
82 - kio-krununittest (Failed)
84 - kio-jobtest (Failed)
92 - kio-kdirlistertest (Failed)
99 - kmimeassociationstest (Failed)
100 - kfile-kfileplacesmodeltest (Failed)
104 - kcookiejartest (Failed)
118 - plasma-plasmoidpackagetest (Failed)
119 - plasma-runnercontexttest (Failed)
120 - plasma-storage (Failed)
Note that ktoolbar_unittest and khtmlparttest passes for me.
Taking a further look on the remaining failures you don't have show that:
11 - kdecore-kdatetimetest (Failed)
18 - kdecore-ktcpsockettest (Failed)
104 - kcookiejartest (Failed)
These tests seems related to locale, as they pass if I export LANG=C, not sure
if we need to do anything about that, or just document that some tests are
only expected to pass with LANG=C.
4 - kdecore-kmountpointtest (Failed)
This one seems to be because the LXC container doesn't contain the device file
in /dev for the block device of any mounted file system, which cases
KMountPoint::Private::finalizePossibleMountPoint to believe no mounts are from
a "real device", at which point KMountPointTest::testCurrentMountPoints() get
nothing to work on, and FAILs. Would also FAIL on a root-on-nfs setup. Should
probably SKIP instead.
8 - kdecore-kshelltest (Failed)
This one is because ${HOME} and the home directory in the passwd database is
not the same (I'm setting HOME to keep my qt4 and qt5 test environments from
polluting each other or my regular home directory). Not sure what to do about
this one.
84 - kio-jobtest (Failed)
This one is because btrfs reports 0 as directory file size (as a directory in
brfs has no data, only metadata), which will cause the total size of the
tested directory to be smaller than expected. I have submitted a "fix" for this
issue (eg reduce the expected minimum total file size).
That only leaves three tests I have no clue about why they are failing.
82 - kio-krununittest (Failed)
92 - kio-kdirlistertest (Failed)
99 - kmimeassociationstest (Failed)
Best Regards
Jon Severinsson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20121214/774bfaa7/attachment.sig>
More information about the Kde-frameworks-devel
mailing list