v3.21
I noticed that when I ran churn mode the test process is restarting every few seconds (dotnet core). Is this intentional behavior and can I change how often it will restart the process?
(The problem in my case is the restart is taking several seconds and I would want to churn in existing process because it is then my test is failing when rerunning it manually from time to time).
Thanks.
Remco NCrunch Developer
#12754
09 Oct 2018 11:33 UTC
Hi,
Yes, this is intentional. Every time a test task is queued by churn mode, there is a small percentage chance (I think 5% or something like that) of the process being recycled.
This is to ensure that churn mode properly churns out sequence related issues that wouldn't show up if test processes were re-used every time. I realise that this could cause an efficiency decrease on some suites that rely on pre-loaded state being in the test process. If it's a big enough problem, I suppose it could be made configurable .. though that would be yet another config setting in our sea of config settings.
Yes, this is intentional. Every time a test task is queued by churn mode, there is a small percentage chance (I think 5% or something like that) of the process being recycled.
This is to ensure that churn mode properly churns out sequence related issues that wouldn't show up if test processes were re-used every time. I realise that this could cause an efficiency decrease on some suites that rely on pre-loaded state being in the test process. If it's a big enough problem, I suppose it could be made configurable .. though that would be yet another config setting in our sea of config settings.
Post a reply
Log in to reply.