On Friday 29 July 2016 10:52:37 David Faure wrote: > On dimanche 24 juillet 2016 16:29:19 CEST Christoph Feck wrote: > > On Sunday 24 July 2016 16:06:52 no-re...@kde.org wrote: > > > BUILD UNSTABLE > > > Build URL: > > > https://build.kde.org/job/kwidgetsaddons%20master%20kf5-qt5/PLA > > > TFO RM=Linux,compiler=gcc/58/ Project: > > > PLATFORM=Linux,compiler=gcc Date of build: Sun, 24 Jul 2016 > > > 13:32:28 +0000 > > > Build duration: 5 min 41 sec > > > > > > JUNIT RESULTS > > > > > > Name: (root) Failed: 1 test(s), Passed: 11 test(s), Skipped: 0 > > > test(s), Total: 12 test(s)Failed: TestSuite.kdualactiontest > > > > autotests/kdualaction passes locally. Any idea why it fails on > > CI? > > I can reproduce it locally by doing > > $ XDG_DATA_DIRS=/foo ./kdualactiontest > (so that installed icon themes are not found) > > and > $ QT_PLUGIN_PATH=/foo XDG_DATA_DIRS=/foo ./kdualactiontest > (so that the platform plugin isn't found, and QIcon's own engine is > used instead of KIconLoader) > > To make sure this didn't come from my kiconthemes changes I also > tested going back to earlier versions, and the bug still happens. > > So my current hypothesis is that it's the changes in QIcon itself, > since the CI was recently switched to 5.7. > This is in fact also shown by the fact that > https://build.kde.org/job/ > kwidgetsaddons%20master%20stable-kf5-qt5/ is green. > (I'm referring to commits 1464118, d3a21a1, e68d067 in qtbase) > > My current assumption would be that the QIcon changes are correct, > so can you double-check if this unittest is actually correct ?
Please see https://git.reviewboard.kde.org/r/128548/ The reason why it worked for me was because I still have the KDE 4 Oxygen theme installed in system paths, so the "kde" icon was always found (even with no platform integration plugin). _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel