Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Clover liverec file gets deleted each time a clover report is generated. How can I avoid it from being deleted?

I have been testing clover and its powerful and user friedly coverage reports and loving it. I seem to have stumbled upon a roadblock. I have set clover to generate db realtime when the application is up and running. To achieve this I have used flushpolicy="threaded" flushinterval="1000" in clover-setup. I can see the db file size getting increased as I use more and more of my application.

But everytime I generate a clover-report the liverec file gets deleted and any further code coverage is not recorded. Is there any way wherein my generating a report will not impact the recordings?

2 answers

1 accepted

0 votes
Answer accepted

Hi Somesh,

liverec file gets deleted and any further code coverage is not recorded

Removal of the .liverec file shall not affect a process of recording code coverage in any way. The .liverec file is being used as an indicator that coverage recording process has not finished yet - the clover-report task will delay report generatoion in such case (by default up to 3 seconds).

and preventing it from loosing track of the live code coverage

I suspect that code coverage is still being recorded and written to disk, actually. Removal of .liverec file just caused that report was generated without a 3-second delay and some areas of your application were not covered yet at this time.

Cheers
Marek

Marek

I tried what you suggested with the additional gap of more than 3 seconds upto more than 5 minutes but there was no change in db file size. Which makes me believe that .liverec file is important for the recording process. I recreated the same scenario without deleting the file and there was a constant increase in db size.

Am I missing something here? Why everytime I generate a report in a running build the .liverec gets deleted and my code coverage does not happen any more. Size of the db remains stagnant.

I'd love to investigate it further. Could you please raise an issue at http://support.atlassian.com and attach build files, logs, database and an html report? We will post an answer on this forum as soon as the problem is resolved.

Can anyone help me out here?

I found a workaround though. If I copy all the clover db files into my windows system from my linux box and generate the report on windows, this way I avoid the liverec from getting deleted and preventing it from loosing track of the live code coverage.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Happy New Year and Welcome New Marketplace Partner Program Partners!

Happy New Year! We hope you all had a safe and restful holiday season. 2020 was a unique year full of unforeseen events; however, as we enter the new year of 2021, we’re optimistic for the light at t...

442 views 5 16
Read article

Community Events

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

Events near you