Re: KDE Gear projects with failing CI (master + stable) (11 March 2026)

Stefan Brüns <[email protected]> Thu, 12 Mar 2026 21:14:38 +0100
Newsgroups gmane.comp.kde.devel.general
Message-ID <3167618.XAFRqVoOGU@nibbler>
On Donnerstag, 12. März 2026 19:10:35 Mitteleuropäische Normalzeit Ben 
Cooksley wrote:
> On Thu, Mar 12, 2026 at 9:57 PM Méven <[email protected]> wrote:
> > Le mer. 11 mars 2026 à 19:59, Albert Astals Cid <[email protected]> a écrit :
> >> Please work on fixing them, otherwise i will remove the failing CI jobs
> >> on
> >> their 4th failing week, it is very important that CI is passing for
> >> multiple
> >> reasons.
> >> 
> >> Good news: 2 repo fixed
> >> 
> >> Bad news: 3 repo started failing, 1 keeps failing
> >> 
> >> dolphin - NEW
> >> 
> >>  * https://invent.kde.org/system/dolphin/-/pipelines/1188508 (master)
> >>  * https://invent.kde.org/system/dolphin/-/pipelines/1187449 (stable)
> >>  
> >>   * dolphinquerytest fails
> > 
> > Those are clearly due to CI Image error: baloo is not compiled/shipped
> > correctly.
> > Qt6.10 and FreeBSD images are concerned but not Qt6.11 one.

The Qt6.11 tests also fail, but the failure is ignored.

> > The failing test is `dolphinquerytest` that tests baloosearch:/ kio
> > protocol provided by baloo.

It tests Dolphins own query parser.
 
> Sorry but you're quite wrong on that, Baloo builds fine, including the
> build of that KIO worker and there is nothing amiss in it's logs or tests.
> See https://invent.kde.org/frameworks/baloo/-/jobs/4135824 and
> https://invent.kde.org/frameworks/baloo/-/jobs/4135826
> 
> Something else must be wrong, likely in Baloo itself. Or Baloo is
> hardcoding install paths.

Can you provide *any* support for this claim? Why "likely in Baloo"?

It has worked fine in the past, and just started to fail 5 days ago. The 
relevant code has not been changed for months, and definitely not during the 
last week.

Also, the failing test exercises some fairly complicated, Dolphin specific 
wrapper around Baloo's code. The called Baloo code is unit tested, so it is 
quite unlikely the code from Baloo is to blame here.

Regards,

Stefan
signature.asc (application/pgp-signature, 232 B)
-----BEGIN PGP SIGNATURE-----

iHkEABECADkWIQSwWRWIpJbl0W4DemNvf0o9jP6qUwUCabMerhsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDIACgkQb39KPYz+qlPctwCgjArjJlmhy0CVxKPeh5Gt
ibG/Zz4AoJ83Zm1p/bJs/rgChmDP4P5CtxFN
=ODeg
-----END PGP SIGNATURE-----