Here's the October 6 report:
hacky2004-all on 06-Oct-2004 Active Time: 3.83 (total), 0 (yours) Build: 4 (total), 4 (successful). Churn: 898|162 (Total Added|Deleted), 235|0 (yours) Commits: 30 (Total|Distinct), 1 (yours) Coverage: 81.4% (Overall), 2574 (covered methods), 589 (uncovered methods) File Metrics: 856 (classes), 3920 (methods), 56982 (LOC) Performance: 26 (total tests), 4 (failures) Review Active Time: (No data summary method available.) Review Issues: (No data summary method available.) Unit Tests: 532|5|1 (Total p|f|e),
Note that the total size is around 56 KLOC.
Now look at last night's report:
hacky2004-all on 07-Oct-2004 Active Time: 10.08 (total), 3.67 (yours) Build: 4 (total), 4 (successful). Churn: 1484|400 (Total Added|Deleted), 0|0 (yours) Commits: 78 (Total|Distinct), 0 (yours) Coverage: 81.3% (Overall), 2582 (covered methods), 592 (uncovered methods) File Metrics: 754 (classes), 3409 (methods), 47934 (LOC) Performance: 26 (total tests), 2 (failures) Unit Tests: 612|10|2 (Total p|f|e), 11|0|1 (yours)
The total size has dropped by almost 10K, even though the Churn data indicates there should be a net increase of 1K to the code! It almost looks like a module has been taken out of hackystat-ALL or something.
Does anyone have any insights into what's going on?
Cheers, Philip
p.s. I continue to hack away on hackyReview. I've rewritten a lot of the package as I've discovered what I think are some interesting design patterns for the DailyProjectData level. I hope to commit in the next few days.
