On Saturday, 4 August 2018 13:06:42 CEST David Faure wrote: > Anyone running FreeBSD, who could to try and debug this hanging unittest > from the ktextwidgets framework? > > https://build.kde.org/view/Frameworks/job/Frameworks%20ktextwidgets%20kf5-qt > 5%20FreeBSDQt5.10/9/testReport/junit/(root)/TestSuite/ktextwidgets_krichtext > edittest/ > > There's no waiting of any kind in the code, it's straight QTextDocument > usage, this shouldn't deadlock or anything. Yet it times out (after 30 > seconds!!) quite often in CI.
I just built master -- after changing the CMakeLists.txt to accept Frameworks
5.46 which I have on my live desktop -- and ran the tests twice with "make
test".
Start 1: ktextwidgets-kfindtest
1/5 Test #1: ktextwidgets-kfindtest .................... Passed 0.45 sec
Start 2: ktextwidgets-kreplacetest
2/5 Test #2: ktextwidgets-kreplacetest ................. Passed 0.60 sec
Start 3: ktextwidgets-krichtextedittest
3/5 Test #3: ktextwidgets-krichtextedittest ............ Passed 0.56 sec
Start 4: ktextwidgets-ktextedit_unittest
4/5 Test #4: ktextwidgets-ktextedit_unittest ........... Passed 0.51 sec
Start 5: ktextwidgets-kpluralhandlingspinboxtest
5/5 Test #5: ktextwidgets-kpluralhandlingspinboxtest ... Passed 0.45 sec
Start 1: ktextwidgets-kfindtest
1/5 Test #1: ktextwidgets-kfindtest .................... Passed 1.03 sec
Start 2: ktextwidgets-kreplacetest
2/5 Test #2: ktextwidgets-kreplacetest ................. Passed 7.48 sec
Start 3: ktextwidgets-krichtextedittest
3/5 Test #3: ktextwidgets-krichtextedittest ............ Passed 0.84 sec
Start 4: ktextwidgets-ktextedit_unittest
4/5 Test #4: ktextwidgets-ktextedit_unittest ........... Passed 1.82 sec
Start 5: ktextwidgets-kpluralhandlingspinboxtest
5/5 Test #5: ktextwidgets-kpluralhandlingspinboxtest ... Passed 1.00 sec
This was on a fairly loaded system (parallel building packages at the same
time) but you can see the time taken for the test is quite large. A third run
even used 20.75 wall-clock seconds.
During the kreplacetest, I can see a window popping up, and then going away,
multiple times. It's weird. But the third test does seem to run successfully
here -- I'll have to dig into how the CI runs the tests, exactly.
[ade]
signature.asc
Description: This is a digitally signed message part.
