It seems that the flushinterval directive is not working with clover 3.1.4. When I run the instrumented code in a JVM nothing is writting to the recordings files until the jvm is shutdown. Here's the clover-setup I'm using in ant to instrument the code.
<clover-setup initstring="/opt/tomcat/temp/clover/clover.db" instrumentationLevel="statement" flushpolicy="interval" flushinterval="1000" />
Once I start the JVM it creates a file named clover.db.liverec in the same directory as my clover.db file however no coverage data is written until the JVM shuts down.
I've also tried flushpolicy="threaded" with the same results.
Hi community members, My name is Erika and I’m a product manager at Atlassian. We’re currently investigating how teams are planning work at the program level. We understand that every team in a tea...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events