KService/sycoca assert in tests on CI

[David Faure]

On Saturday 23 April 2016 00:51:28 Daniel Vrátil wrote:
> Hi guys,
> 
> some KDE PIM unit tests are failing on the CI due to an assert in ksycoca, for 
> example here: [0]
> 
> QWARN  : TestBlogger1::testNetwork() kf5.kservice.sycoca: ERROR: KSycoca 
> database corruption!
> QWARN  : TestBlogger1::testNetwork() kf5.kservice.sycoca: ERROR: KSycoca 
> database corruption!
> QWARN  : TestBlogger1::testNetwork() kf5.kservice.sycoca: ERROR: KSycoca 
> database corruption!
> QWARN  : TestBlogger1::testNetwork() kf5.kservice.sycoca: ERROR: KSycoca 
> database corruption!
> QDEBUG : TestBlogger1::testNetwork() Recreating ksycoca file ("/home/
> jenkins/.qttest/cache/ksycoca5_C_446ImL1tUTkflcd3IPkQK3mGYhc=", version 303)
> QDEBUG : TestBlogger1::testNetwork() Menu "applications-kmenuedit.menu" not 
> found.
> QDEBUG : TestBlogger1::testNetwork() Saving
> QWARN  : TestBlogger1::testNetwork() kf5.kservice.sycoca: ERROR: KSycoca 
> database corruption!
> QFATAL : TestBlogger1::testNetwork() ASSERT: "!dirs.isEmpty()" in file /home/
> jenkins/sources/kservice/stable-kf5-qt5/src/sycoca/ksycoca.cpp, line 626
> 
> It works locally, so it's possible it's something on the CI, altought we've 
> been seeing this problem for quite a while (even before switch to Docker). Any 
> ideas what's going on there? Is it a problem on the CI side, our side or maybe 
> something in sycoca?

This is very likely fixed by 90e71d5 in kservice (with thanks to Jos van den Over for the fix).

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5