On Sun, Nov 17, 2019 at 7:48 AM Simon Redman <si...@ergotech.com> wrote: > > My only thought about this is, is it possible to disable the tests in a > way which leaves a warning so that at least it isn't silently "passing"?
If they are disabled in the way I am suggesting, they wouldn't even be registered with CTest. Cheers, Ben > > On 11/15/19 10:02 PM, Ben Cooksley wrote: > > Hi all, > > > > For some time now the Akonadi Test Runner infrastructure has had > > issues on the CI system where it will fail to properly shutdown the > > akonadiserver (and associated subprocesses) that it starts up for > > tests. > > > > This leads to jobs on the CI system becoming indefinitely stuck as > > CTest will wait indefinitely for subprocesses spawned by tests to > > exit. This in turn requires manual cleanup. > > > > Tonight jobs for kdepim-runtime and akonadi itself both required > > manual assistance to complete. Other PIM repositories have in the past > > required similar assistance. > > > > Given that the issue is not limited to a single test or repository, > > i'd therefore like to propose no-oping the entire CMake macro > > responsible for the akonadi test runner framework and disabling all > > tests that make use of it globally across all repositories until this > > issue can be rectified. > > > > Regards, > > Ben >
