Hi - We are using Clover Version 3.1.10, built on January 08 2013 (build-885).
Reports used to take 25 minutes to generate. Over time the duration has been increasing and become dependent on the numerical order when the reports are produced. That is to say, not only is the duration increasing in general, but 3rd report takes longer than the 1st, 45 minutes vs. 2.5 hours. We have 20 reports to generate and don't finish in 24 hours.
Example of console log out of the first report:
02:25:01 [clover-report] Loaded from: /data/jenkins-slave/workspace/codecov/src/buildtools/lib/clover-ant-3.1.10/lib/clover.jar 02:25:01 [clover-report] Loading coverage database from: '/data/jenkins-slave/workspace/codecov/src/.clover/clover3_1_10.db' 03:13:30 [clover-report] Writing HTML report to '/data/jenkins-slave/workspace/codecov/src/bin/BuildReports/udp_codecov' 03:15:11 [clover-report] Done. Processed 46 packages in 100606ms (2187ms per package).
Example of the 3rd report
06:54:46 [clover-report] Loaded from: /data/jenkins-slave/workspace/codecov/src/buildtools/lib/clover-ant-3.1.10/lib/clover.jar 06:54:46 [clover-report] Loading coverage database from: '/data/jenkins-slave/workspace/codecov/src/.clover/clover3_1_10.db' 09:23:46 [clover-report] Writing HTML report to '/data/jenkins-slave/workspace/codecov/src/bin/BuildReports/hoteldomain_codecov' 09:30:27 [clover-report] Done.
Background info:
Running on Linux with 32GB RAM
Remedial actions taken:
We were seeing out of memory errors so we split the Jenkins code coverage job into 2 parts:
I have manually deleted the .clover folder, killed the jenkins process, restarted the box, restarted the jenkins process to no avail.
Has anyone seen this and (hopefully!) rectified the situation?
Thanks.
Tim
Ran “ps aux | grep "java"” and noticed there was 1 instance of Clover running
Additional info: The .clover db folder used to be 3 GB. What currently gets produced is 4.5 GB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.