-
Bug
-
Resolution: Fixed
-
Highest
-
3.1.8
-
None
-
Redhat 6.1, Sun 64-bit JVM, 1.6.0_34, Grails 2.1.1 with plugin version 3.1.8
For some reason, in our Grails test environment, clover is stuck in what seems to be an infinite loop recording the data for all the files instrumented during the run.
This occurs at the end of a run started with "grails test-app -clover.on" which runs both unit and integration tests.
Our project is fairly reasonable in size:
+----------------------+-------+-------+
| Name | Files | LOC |
+----------------------+-------+-------+
| Controllers | 8 | 435 |
| Domain Classes | 401 | 18552 |
| Services | 36 | 4773 |
| Tag Libraries | 5 | 790 |
| Groovy Helpers | 345 | 17830 |
| Java Helpers | 3 | 141 |
| Unit Tests | 68 | 5040 |
| Integration Tests | 401 | 14290 |
| Scripts | 6 | 83 |
+----------------------+-------+-------+
| Totals | 1273 | 61934 |
+----------------------+-------+-------+
During the run, Clover generates an amazing number of files in the .clover/ directory (about 600,000 files *.s files)
At the end of the run we get:
[Step 2/3] | Completed 563 integration tests, 0 failed in 328038ms [09:31:13][Step 2/3] | Tests PASSED - view reports in /home/teamcity/TeamCity/buildAgent1/work/7f907064610a9f8f/common/target/test-reports [09:31:13][Step 2/3] Clover: Tests ended [09:31:13][Step 2/3] Clover: Generating report using default 'clover-report' task
I've attached a chunk of the log file looping on the report generation, the full log file is 4GB before I stopped it.
Also, I've attached a stack trace taken while it is seemingly looping.
It's weird, we are evaluating clover and it works fine on our other project module, but not this one. The configuration is the same:
clover {
excludes = ['**/conf/**', '**/plugins/**', '**/migrations/**', '**/drillDown/**', '**/generator/**']
initstring = ".clover/common.db"
}
- blocks
-
-
- Closed
-