Closed velo closed 9 years ago
I have the same issue. I use gradle plugin and it works only if property targetClasses has narrower package to check (e.g. com.my.auction.core.crypto.* instead of **com.my.auction.***).
This may be the same issue as
https://github.com/hcoles/triangle-example/issues/1
If you disable verbose logging do you still experience the hang?
Not helped. This is my confog in gradle:
pitest {
targetClasses = ['com.bas.auction.core.*'] //by default "${project.group}.*"
threads = 4
maxMutationsPerClass = 2
excludedMethods = ['hasCode', 'equals']
outputFormats = ['HTML']
jvmArgs = ['-Xmx1024m']
verbose = false
}
It hangs without any observable activity (i.e. cpu is idle)
@agzamovr I think you may be experiencing a different issue than @velo - could you raise it under a separate defect.
Makes no difference. With or without verbose it hangs
@velo I've just pushed a 1.1.7-SNAPSHOT to the sonatype snapshot repo (https://oss.sonatype.org/content/repositories/snapshots/org/pitest/)
Can you confirm if you can still reproduce the issue using the snapshot?
SUCCESS!!
@velo Excellent, I'll push a release out soon.
Thanks for the report.
Outstanding, thanks @hcoles
Fixed in 1.1.7
Thank you for this... I was actually hitting this issue very often, but I thought that it was an issue with how my tests were written. This makes pitest actually usable :)
So, I was using pitest-maven-plugin 1.1.5 and all was good.
When I decided to move to 1.1.6 my build hangs (waited for 3 hours, still no result)
And that is it.
pom.xml
Is there any other information that I can provide?