Hi David, Unfortunately it doesn't look like the fix we put in place on Saturday did the trick.
I have a feeling that QStandardPaths on Windows at least will also consider the Qt install prefix in addition to the local to the executable paths when searching for mime information. That would explain why the other tests are working and why making that change didn't fix it. Any ideas why this still fails? Cheers, Ben On Sun, Aug 12, 2018 at 3:32 AM CI System <nore...@kde.org> wrote: > *BUILD UNSTABLE* > Build URL > https://build.kde.org/job/Frameworks%20kservice%20kf5-qt5%20WindowsMSVCQt5.10/41/ > Project: Frameworks kservice kf5-qt5 WindowsMSVCQt5.10 > Date of build: Sat, 11 Aug 2018 15:19:21 +0000 > Build duration: 12 min and counting > * JUnit Tests * > Name: (root) Failed: 1 test(s), Passed: 9 test(s), Skipped: 0 test(s), > Total: 10 test(s) > > > * - Failed: TestSuite.kmimeassociationstest* >
