It seems unit tests for ECM are not run on CI, despite there being a stage.
With ECMGenerateExportHeader I have added some longer running tests (totally up to 1 min locally) but wondered when CI passed the stage in a few secs, with no result logging, e.g.
[Pipeline] stage [Pipeline] { (Running Tests) [Pipeline] sh 18:02:25 + python3 -u ci-tooling/helpers/run-tests.py --product Frameworks --project extra-cmake-modules --branchGroup kf5-qt5 --platform SUSEQt5.12 --usingInstall /home/jenkins//install-prefix/ [Pipeline] junit 18:02:25 Recording test results 18:02:26 None of the test reports contained any result [Pipeline] } [Pipeline] // stage
From https://build.kde.org/job/Frameworks/job/extra-cmake-modules/job/kf5-qt5%20SUSEQt5.12/58/console
Is that on purpose, or did something break?