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