Fixing tests failing on CI but not on local system
Ben Cooksley
bcooksley at kde.org
Tue Apr 22 19:57:53 BST 2025
On Wed, Apr 23, 2025 at 5:24 AM Stefano Crocco <stefano.crocco at alice.it>
wrote:
> Hello to everyone,
>
Hi Stefano,
> recently, I've being trying to fix failing Konqueror tests, and in doing
> so I'm
> facing some issue with the CI tests which I don't know how to solve.
>
> The first issue is that one test passes on my system but fails when run by
> the
> CI (it's the konqview test at [1]). I couldn't spot anything in the code
> which
> would be likely to be different on the CI than on my system. What do you
> think
> is the best way to try and fix this test? Should I try and add some
> debugging
> statement in the tests, then run it again on the CI to try to pinpoint the
> cause of the failure? I wouldn't want to waste CI resources, but I have no
> better idea.
>
This test looks like it might be a KXMLGUI initialisation failure:
QWARN : KonqViewTest::textThenHtml() kf.xmlgui: cannot find .rc file
"konqueror.rc" for component "konqviewtest"
QWARN : KonqViewTest::textThenHtml() kf.xmlgui: cannot find .rc file
"konqueror.rc" for component "konqviewtest"
It is probably masked on your local system because there will be old files
/ configuration / etc present.
Might be worth creating a new user account, doing a build of Konqueror
alone there (without logging in or running Konqueror normally there) and
seeing if the unit test fails there as that is basically what CI does.
>
> A similar issue regards tests failing on FreeBSD but not on Linux: how
> should
> I proceed, since that I have no FreeBSD machine available and I'm not
> familiar
> enough with it to try setting up a virtual machine?
>
In the not too distant future once we have VM based CI you'd be able to
download the VM image the CI system uses.
This is weeks, not months, away at this point.
>
> Lastly, there's a test (konqviewmgrtest at [2]) which is marked as failed
> by
> the CI but, looking at the output it reports, seems successful to me (I
> can't
> see any mention of failing tests or errors in the output). I attach a file
> with
> the output of the test. My only guess is that the word "failed" which
> appears
> in lines 3 and 28 but which is unrelated to the test itself may be
> confusing
> the CI. Do you think it is possible? Otherwise, do you have any idea about
> why
> the test could be marked as failed?
>
Reading the full build log reveals why that happened:
4/12 Test #4: konqviewmgrtest ...................***Timeout 60.12 sec
My guess would be that it is popping up a message box as something didn't
quite work out when it tries to activate the link:
QDEBUG : ViewMgrTest::testLinkedViews() ACTIVATING LINK
> Thanks in advance
>
> Stefano
>
Hope that gives you some ideas!
Cheers,
Ben
>
> [1]
> https://invent.kde.org/network/konqueror/-/pipelines/929647/test_report?
> job_name=suse_tumbleweed_qt68
> <https://invent.kde.org/network/konqueror/-/pipelines/929647/test_report?job_name=suse_tumbleweed_qt68>
> [2]
> https://invent.kde.org/network/konqueror/-/pipelines/936026/test_report?
> job_name=suse_tumbleweed_qt69
> <https://invent.kde.org/network/konqueror/-/pipelines/936026/test_report?job_name=suse_tumbleweed_qt69>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20250423/438a8168/attachment.htm>
More information about the kde-devel
mailing list