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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Community! me again 🙂 If you’re a marketing team using Confluence, we want to hear your story! How did you start using Confluence? What are your use cases? What have been some of the benefits?...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs