This message was deleted.

I think that depends on the scenario. Normally this isn't the case in a single scenario, but the daemon will be stopped when starting a new scnario. What scenario are you testing?

A clean build with no daemon. The problem is actually gradle-profiler stopping all the daemons before starting the scenario on a CI machine. That would fail other jobs running concurrently

That is to ensure a consistent result.

Ok, that was my initial guess. Thanks for your attention