clover flushinterval not working with interval or threaded flushpolicy

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.

2 answers

I am also facing the same issue.

Please help.

In my case, I don't get code coverage even after I shut down Tomcat... Tried with Interval at 5000. Even my liverec file does not go away after I shut down tomcat.. Please help.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

258 views 0 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you