Hopefully these work okay and don't end up causing too many issues, but at the very least it should be contained to 2 Docker containers and won't block other projects building too badly.

CCMAIL: faure@kde.org

This will ensure that should test executables not be found, we will flag them as failures for further investigation rather than silently ignoring them.

Differential Revision: https://phabricator.kde.org/D20874

Differential Revision: https://phabricator.kde.org/D20769

Both messagelib and mailcommon also use the same Akonadi Server test framework which doesn't exit properly.
All of these hanging cases are likely ultimately the same bug sadly.

CCMAIL: kde-pim@kde.org

Fixes T10800

CCMAIL: elisa@kde.org

CCMAIL: kde-pim@kde.org

The test kblog-testblogger1 causes kdeinit5 to be relaunched (or alternatively, kblog-testblogcomment kills it), which guarantees that ctest will always hang following the completion of this test.
It also means that manual intervention is required for every test process after that one, as kdeinit5/klauncher/kded will all have to be killed following the completion of the individual test.

Therefore, to avoid the need for manual intervention to keep the CI system working we are disabling the execution of tests for kblog.

CCMAIL: kde-pim@kde.org
CCMAIL: release-team@kde.org

This will reduce the test timeout from 10 minutes to 1 minute as well, which should reduce the impact of hanging tests by 10x

Therefore bring it in as well

Despite repeated manual kicks to clear stuck akonadiserver/akonadi_knut_resource/akonadi_control processes, it has failed to progress itself and is just tying up a builder.

This should also correct the breakage which is currently causing all Frameworks Linux builds to have an UNSTABLE (failing tests) status as the YAML depreciation warnings were causing the check-platforms logic to trip.

CCMAIL: kde-frameworks-devel@kde.org

Otherwise they aren't accessible

runner is out of service

This way it's easier to reuse these parts of the logic

And if so, build them against the host system

It's needed for native builds if we're not cleaning them up

Otherwise it's built for ARM

Needed for KArchive native tooling, which in turn is needed for KPackage

It's needed for ki18n

Fixes T10748

Fixes T10749

CCMAIL: faure@kde.org

Fixes T10726

Fixes T10621

It's a CI, it doesn't need full history for development.