Hi,
Does anyone have any experience running Clover on largish projects?
I'm trying to get Clover running for Derby, which has around 500'000+
lines of code (excluding blank lines and comments) and somewhere around
10'000+ test cases (differs hugely wrt size/complexity).
Since this is a database, I assume most of the tests involves executing
the core pieces of the database engine.
I have managed to run most of the tests with Clover. The Clover database
currently weighs in at 4.7 GB, and one of the "half-baked" reports is
5.7 GB big.
Now, when I try to generate the HTML report, it always fails with
out-of-memory exceptions. I'm currently running with
'<clover-html-report numThreads="0" maxtestsperfile="10"/>', using
Clover 2.4.3.
I've tried running with a heap of 5 GB, but still I get OOMEs. This
suggests to me that Clover report generation isn't really written to
process large amounts of data. I can increase the heap further, but then
I'll be using almost all the memory on the slave, which I'd prefer not
to do...
I've seen some other knobs introduced in Clover 2.6.
Is it worth upgrading to 2.6? Is it a lot better?
Any other ways I can make this work?
Alternative tools?
(Apache Derby build is ant based)
I know some of these questions are rather basic, but I'm hoping for some
valuable input as this is a side-project to which I cannot devote that
much time at the moment.
Regards,
--
Kristian
