PIT >> WARNING : Slave exited abnormally due to TIMED_OUT

[Rune Engseth]

Hi

I'm trying out pitest (maven) for the first time.
The codebase consists of > 200.000 lines of Java with about 10.000 tests.

When running pitest maven plugin on the lot, a warning is logged every 4 seconds.
This does not happen for the first modules, however, after a while these warnings are consistently logged


Does anybody know what the implications are?
And should I perhaps tweak the config?

regards
Rune

[INFO] 
build	24-sep-2014 14:52:55	[INFO] --- pitest-maven:1.0.0:mutationCoverage (default-cli) @ reku-domain ---
build	24-sep-2014 14:52:55	[INFO] Found plugin : Default csv report plugin
build	24-sep-2014 14:52:55	[INFO] Found plugin : Default xml report plugin
build	24-sep-2014 14:52:55	[INFO] Found plugin : Default html report plugin
build	24-sep-2014 14:52:55	[INFO] Found plugin : Default limit mutations plugin
build	24-sep-2014 14:52:55	[INFO] Found shared classpath plugin : Default mutation engine
error	24-sep-2014 14:52:55	14:52:55 PIT >> INFO : Mutating from ..target\classes
error	24-sep-2014 14:52:55	14:52:55 PIT >> INFO : Verbose logging is disabled. If you encounter an problem please enable it before reporting an issue.
error	24-sep-2014 14:52:56	14:52:56 PIT >> INFO : Sending 165 test classes to slave
error	24-sep-2014 14:52:56	14:52:56 PIT >> INFO : Sent tests to slave
error	24-sep-2014 14:52:58	14:52:58 PIT >> INFO : SLAVE : 14:52:58 PIT >> INFO : Found  1302 tests
error	24-sep-2014 14:52:58	14:52:58 PIT >> INFO : Dependency analysis reduced number of potential tests by 0
error	24-sep-2014 14:52:58	14:52:58 PIT >> INFO : 1302 tests received
error	24-sep-2014 14:52:58	
error	24-sep-2014 14:52:58	14:52:58 PIT >> INFO : SLAVE : Missing required option: bps
error	24-sep-2014 14:52:58	14:52:58 PIT >> INFO : SLAVE : 
error	24-sep-2014 14:52:58	
error	24-sep-2014 14:52:58	14:52:58 PIT >> INFO : SLAVE : Missing argument for option: bps
error	24-sep-2014 14:52:58	14:52:58 PIT >> INFO : SLAVE : 
error	24-sep-2014 14:52:58	
error	24-sep-2014 14:52:58	14:52:58 PIT >> INFO : SLAVE : Missing required option: env
error	24-sep-2014 14:52:58	14:52:58 PIT >> INFO : SLAVE : 
error	24-sep-2014 14:52:58	
error	24-sep-2014 14:52:59	14:52:59 PIT >> INFO : SLAVE : Missing required option: fips
error	24-sep-2014 14:52:59	14:52:59 PIT >> INFO : SLAVE : 
error	24-sep-2014 14:52:59	
error	24-sep-2014 14:52:59	14:52:59 PIT >> INFO : SLAVE : Missing argument for option: fips
error	24-sep-2014 14:52:59	14:52:59 PIT >> INFO : SLAVE : 
error	24-sep-2014 14:52:59	
error	24-sep-2014 14:52:59	14:52:59 PIT >> INFO : SLAVE : Missing required option: env
error	24-sep-2014 14:52:59	14:52:59 PIT >> INFO : SLAVE : 
error	24-sep-2014 14:52:59	
error	24-sep-2014 14:53:12	14:53:12 PIT >> INFO : Calculated coverage in 17 seconds.
error	24-sep-2014 14:53:13	14:53:13 PIT >> INFO : Created  421 mutation test units
error	24-sep-2014 14:53:28	14:53:28 PIT >> WARNING : Slave exited abnormally due to TIMED_OUT
error	24-sep-2014 14:53:36	14:53:36 PIT >> WARNING : Slave exited abnormally due to TIMED_OUT
error	24-sep-2014 14:53:41	14:53:41 PIT >> WARNING : Slave exited abnormally due to TIMED_OUT
error	24-sep-2014 14:53:50	14:53:50 PIT >> WARNING : Slave exited abnormally due to TIMED_OUT
error	24-sep-2014 14:53:58	14:53:58 PIT >> WARNING : Slave exited abnormally due to TIMED_OUT

...

[henry]

On Wednesday, 24 September 2014 14:31:40 UTC+1, Rune Engseth wrote:

When running pitest maven plugin on the lot, a warning is logged every 4 seconds.
This does not happen for the first modules, however, after a while these warnings are consistently logged

Does anybody know what the implications are?
And should I perhaps tweak the config?

 This isn't necessarily anything to worry about, pitest will log this message every time it thinks it has encountered an infinite loop. If you see a lot of these messages it could however mean that pitest is being a bit hasty in marking something as an infinite loop (see the faq for an explanation of why this happens http://pitest.org/faq/).

Take a look at the generated report - if the mutations marked as timed out don't look like infinite loops to you try a larger value for the timeout const. The only downside of increasing this value is that it will slow down the process by causing a longer wait each time an infinite loop is encountered.

Henry

[Rune Engseth]

Thanks for info

I'll try to adjust the timeout setting, and see if it has any effect