Guys, KTextEditor is the worst KF5 framework now, for a month, in terms of unittests. It's been broken for a month, and nobody replied to my previous email on the topic.
Everything else is green, KTextEditor is the only framework which is not - on the day of the release, two months in a row. https://build.kde.org/job/ktexteditor%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/90/console 42/53 Test #42: completion_test .........................***Failed 62.16 sec 11:18:28 ********* Start testing of CompletionTest ********* 11:18:28 Config: Using QtTest library 5.5.1, Qt 5.5.1 (x86_64-little_endian-lp64 shared (dynamic) debug build; by GCC 4.9.2) 11:18:28 PASS : CompletionTest::initTestCase() 11:18:28 QDEBUG : CompletionTest::testFilterEmptyRange() "a" 11:18:28 FAIL! : CompletionTest::testFilterEmptyRange() Compared values are not the same 11:18:28 Actual (countItems(model)): 0 11:18:28 Expected (40) : 40 11:18:28 Loc: [/home/jenkins/builds/ktexteditor/kf5-qt5/autotests/src/completion_test.cpp(117)] 11:18:28 QDEBUG : CompletionTest::testFilterWithRange() "a" 11:18:28 FAIL! : CompletionTest::testFilterWithRange() Compared values are not the same 11:18:28 Actual (countItems(model)): 0 11:18:28 Expected (14) : 14 11:18:28 Loc: [/home/jenkins/builds/ktexteditor/kf5-qt5/autotests/src/completion_test.cpp(133)] As said previously, I took the time to git bisect, and it appears the breakage isn't from the ktexteditor framework itself, so I suspect it's in one of its dependencies. Still, debugging this requires knowing how the ktexteditor completion code works... -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5 _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
