Re: Excessive tests in Ruqola / dependencies not built as part of the Craft caches
laurent Montel <[email protected]> Thu, 16 Jul 2026 14:48:57 +0200
| Newsgroups | gmane.comp.kde.devel.core,gmane.comp.kde.devel.general |
|---|---|
| Organization | kde2 |
| Message-ID | <[email protected]> |
Le jeudi 16 juillet 2026, 14:38:57 heure d=E2=80=99=C3=A9t=C3=A9 d=E2=80=99= Europe 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 complaints > >> regarding a lack of CI builder availability, primarily from those who = 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 done= in 6 > >> minutes - with many of these being less than 1 second to run). Given t= hat > >> every single one of these unit tests needs to have automoc / compiler / > >> linker run on it i'd suggest that similar tests be merged into the same > >> compilation unit (you can run the individual tests, but keep similar t= ests > >> 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-next > > It's the main target. but I need to know how to told to CI to exclude o= ther 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. ok =3D> we can exclude all autotests from windows/freebsd =3D> we will reduce timeout. We don't have a environment variable which informs that we are on CI ? =3D> I can exclude building on CI + specific platform. ok I can add a=20 Options: cmake-options: "-DDISABLE_AUTOTEST=3DTRUE" in ruqola code in CMakeLists.txt if(WIN32 AND APPLE AND DISABLE_AUTOTEST) set(BUILD_TESTING FALSE) endif() I think that cmake can test freebsd too. =3D> we will reduce building autotests.