After the recent discussions on state of CI, I fixed the last unittest failures (kio, purpose... + apol fixed ECM) so that https://build.kde.org/job/Frameworks/view/Platform%20-%20SUSEQt5.15/ is all green^H^Hblue again. Please keep it that way!
Note however that * kwayland has a flaky test: https://build.kde.org/job/Frameworks/view/Platform%20-%20SUSEQt5.15/job/kwayland/job/kf5-qt5%20SUSEQt5.15/171/testReport/junit/projectroot.autotests/client/kwayland_testDataDevice/ FAIL! : TestDataDevice::testReplaceSource() Compared values are not the same Actual (selectionOfferedSpy.count()): 1 Expected (2) : 2 Loc: [autotests/client/test_datadevice.cpp(557)] Who can look at this one? git log mostly shows Martin Flöser <mgraess...@kde.org> who I think isn't active anymore? * krunner has a flaky test [2] because it measures time spent and expects small values like 65ms (I changed that one to 100ms), 250ms, 300ms. With only 10% safety margins. On a busy CI system, this is bound to fail regularly, even with bigger safety margins. In my experience this kind of test is just not possible (we're not running on a real time OS), I vote for removing the test. CC'ing Eduardo. https://build.kde.org/job/Frameworks/view/Platform%20-%20SUSEQt5.15/job/krunner/job/kf5-qt5%20SUSEQt5.15/325/testReport/junit/projectroot/autotests/runnermanagertest/ -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
