Henry Coles
Henry Coles
The initial use case is support for a `.pitest` directory at the root of the project to store config for all projects within it. It wouldn't be relevent for aggregation.
The idea of the .pitest directory is to provide config without having to update each of the build integrations. The initial thinking is to use it for things best expressed...
This will be addressed in pitest 1.7.1, which adds a new "verbosity" param, with options to enable/disable the spinner and swallow a lot of the noise from the minions. https://github.com/hcoles/pitest/pull/934
The scmMutationCoverage is built on top of the maven source control abstraction, so I don't think it would be easy to port to gradle. It also has a few issues...
If you enable verbose logging it may give some information about the cause of the RUN_ERRORs. Also, please note that you almost certainly do not want to enable "ALL" mutators...
@sharath2106 Did you try enabling verbose logging?
The [Arcmutate extended operators](https://docs.arcmutate.com/docs/extended-operators.html) provide stream api operators and more.
The error looks to be occuring in the minion launched to gather block coverage, so gc parameters need to be passed to the child process. This can be done using...
> Thanks! As you can see I already use jvmArgs. Is there anything am I missing? Sorry, I completely misread the command line. That looks correct to me for passing...
@mgonzcast Can you give an indication of how large this module is? How long do the tests take to run wihtout pitest? Roughly how many thousand lines of code is...