On Saturday, 16 November 2019 06:39:29 CET Ben Cooksley wrote: > Hi all, > > Currently we have an issue where the test 'testkioarchive' within > kio-extras causes kdeinit5 to be relaunched, as can be seen in the CI > run log below. > > https://build.kde.org/job/Applications/job/kio-extras/job/kf5-qt5%20SUSEQt5. > 12/40/console > > This is behaviour which is not permitted within the CI system, as the > newly spawned 'kdeinit5' processes are treated as being launched by > that test by CTest, meaning it will wait for eternity for them to exit > (which as resident daemon processes, they will not do without manual > intervention). > > This in turn blocks the job from completing, and blocks CI resources > in the process. > > I'd therefore like to propose disabling this test across all platforms > as it's behaviour is incompatible with the CI system. > > It is the sole and exclusive responsibility of the CI tooling to > ensure that kdeinit5 is started with the appropriate environment, and > this should not be tampered with by tests under any circumstances.
Same issue as with kdav I think, the test just runs a KIO job. Same fix applied, let's see if that helps. Regards, Volker
signature.asc
Description: This is a digitally signed message part.
