On Sat, 13 Apr 2019, 07:35 Ben Cooksley, <bcooks...@kde.org> wrote: > Hi all, > > Currently we have an issue where the test_crasher test will endlessly > fork itself while trying to setup it's conditions to run. > > This leads to an issue where it will occupy a single CPU core of a > builder indefinitely until it's killed (and when killed there are > always two test_crasher.exe processes running, and if not killed > simultaneously it won't move on to the next test) > > Any ideas on how to resolve this? > > (This has existed for some time, i've just not had the time to raise > it as an issue) >
Gentle ping? Anyone with any thoughts on this? > Cheers, > Ben > Thanks, Ben >
