Re: Excessive tests in Ruqola / dependencies not built as part of the Craft caches

--nextPart2245001.9o76ZdvQCi
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Thomas Baumgart <[email protected]>
To: [email protected]
Cc: [email protected]
Date: Thu, 16 Jul 2026 16:41:21 +0200
Message-ID: <4916842.vXUDI8C0e8@sy-346-nb>
In-Reply-To: <[email protected]>
MIME-Version: 1.0

On Donnerstag, 16. Juli 2026 14:48:57 Mitteleurop=C3=A4ische Sommerzeit lau=
rent Montel wrote:

> Le jeudi 16 juillet 2026, 14:38:57 heure d=E2=80=99=C3=A9t=C3=A9 d=E2=80=
=99Europe centrale Vlad Zahorodnii a =C3=A9crit :
> > Hi,
> >=20
> > On 7/16/26 3:00 PM, laurent Montel wrote:
> > > Le jeudi 16 juillet 2026, 13:35:05 heure d=E2=80=99=C3=A9t=C3=A9 d=E2=
=80=99Europe centrale Ben Cooksley a =C3=A9crit :
> > >> Hi Laurent, all,
> > > Hi,
> > >
> > >> Over the past week or two Sysadmin has received a number of complain=
ts
> > >> regarding a lack of CI builder availability, primarily from those wh=
o work
> > >> on Plasma. Investigation has revealed that Ruqola appears to use a
> > >> disproportionately high amount of CI time compared to the size of the
> > >> project and it's activity.
> > >>
> > >> This appears to be driven by the fact that Ruqola has a large number=
 of
> > >> tests that do not take very long to execute (700 or so tests, yet do=
ne in 6
> > >> minutes - with many of these being less than 1 second to run). Given=
 that
> > >> every single one of these unit tests needs to have automoc / compile=
r /
> > >> linker run on it i'd suggest that similar tests be merged into the s=
ame
> > >> compilation unit (you can run the individual tests, but keep similar=
 tests
> > >> together in the same unit test).
> > > In ruqola each autotest depends against a specific class.
> > > So merging them in one autotest seems not logical.
> > > It's the same idea that merging autotests from kio in one autotest.
> > >
> > > After that I am not against to execute autotests only on linux-qt6-ne=
xt
> > > It's the main target. but I need to know how to told to CI to exclude=
 other platforms.
> >=20
> > If you're looking for a way to run tests only on a specific platform,=20
> > there is `run-tests-on: []` option in `.kde-ci.yml`. If you're looking=
=20
> > for a way to also disable building those tests, I'm not sure.
>=20
> ok =3D> we can exclude all autotests from windows/freebsd
> =3D> we will reduce timeout.
>=20
> We don't have a environment variable which informs that we are on CI ?
> =3D> I can exclude building on CI + specific platform.

I just added that logic to my work project (catching Gitlab and Azure DevOp=
s):

# -------------------------------
# Detect environment: developer or pipeline
# -------------------------------
if(DEFINED ENV{CI} OR DEFINED ENV{GITLAB_CI} OR DEFINED ENV{TF_BUILD})
    set(IS_PIPELINE TRUE)
else()
    set(IS_PIPELINE FALSE)
endif()


=2D-=20

Regards

Thomas Baumgart

=2D------------------------------------------------------------
Life is a journey, not a race! (unknown source)
=2D------------------------------------------------------------

--nextPart2245001.9o76ZdvQCi
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Comment: https://blog.bembel.net/

iQIzBAABCgAdFiEEldM0sAUOY2HYD2VASQpC8iaztXcFAmpY7ZEACgkQSQpC8iaz
tXc4Cg//VkJeitxrBpqg+Ht0TH03s2j25oGwXGmcVB1YkBPO4Kj3y720trxx9Wu+
mncopqzG5nYUumGSCHU+onzebauo1hQqIQ/mgIkPFqGDRKRb13+K0fV1Jhdyk3u4
YN//hmzY9dEcYsB31IGeALDWylQbS5N6HA1Jn0uENmgDCR/DR/Gj6rQy/+64wYyU
lL5jZmr1tiW1mIMM/hFINkHQwsmkc6WRMbljPc784lhcnyQ8uGkHXH+1UFiLmhPP
AEXIpVhpBHWYT9F6BNTUqQArwcTpcwbPFzHv2SCzr3YzqZ4zKcn7PpXH+0kPjE2z
KoP6+uBQypjdN1HCB2ieZfNJoB2VEo9P77EbjJEr4mlYiJ8ro8kO2HER95xxzONN
5YiKcbAoZeOvvCUU0kwENoewnCqS4hHojRUfdneu/4TjwzybNvXncL95M8XAD/kB
TSvZKQC5IvYor1tCLIyyBd79CW+q9HCpgoNmRIfXafrVvhiwHzX4sN9q4FqITWxo
W+39LJl3ivdUbnjQ9rXF9COrme0VYK8lqoYAgfTjNzO4ERQ1wQK5/YxEJj8mfGVS
LXdCXcY2zsdAWQalghU6Xz+5jnxVSz4NqdorKEu8ZmET9KHpHdJWIkZkBGIeg+ui
Cxkl9hBgIX3pISrgYw4sGU0O4ytIDfL4BE1jU1XUvig8GrmpvTs=
=+SOO
-----END PGP SIGNATURE-----

--nextPart2245001.9o76ZdvQCi--