Sorry, a typo
DistinctCommit(day 1 and 2) = 1 which may not be what you want.
should be read as
DistinctCommit(day 1 and 2) = 2 which may not be what you want.
(Cedric) Qin ZHANG wrote:
Hi, Aaron,
Dependency:
I sent you an email yesterday about that. Maybe you missed it. It was
caused by bad sdt evolution. I made some commits yesterday. The
DailyProjectDependency2 which is used by the reducer should be ok now.
The problem is DailyProjectDependency which is used by a dependency
analysis written by you a while ago. It can handle pre-evolution data
because they have class name. But I am not sure how it can handle
post-evolution data, since they only contains file path.
Ref: http://hackydev.ics.hawaii.edu:8080/browse/HACK-615
Perhaps you can close 732 and 727 if they are duplicate of 615.
Commit:
There is one potential problem with distinct commit. Consider the
following case:
day 1: file A committed twice
day 2: file A committed twice
In current implementation,
DistinctCommit(day 1) = 1
DistinctCommit(day 2) = 1
DistinctCommit(day 1 and 2) = 1 which may not be what you want.
Build:
No comment.
Cheers,
Cedric
Aaron Kagawa wrote:
Hey Guys,
Dependency:
As Cedric pointed out today, the Dependency data isn't showing up in
any of the analyses. I investigated this a while ago, and didn't get
to far: http://hackydev.ics.hawaii.edu:8080/browse/HACK-732 and
http://hackydev.ics.hawaii.edu:8080/browse/HACK-727 .
Commit:
Austen was suggested that we should change the Commit Summary and
Drill Down data to include the number of distinct commits. I would
agree that would be useful information. Philip if you agree that
this would be useful, I think Austen can handle making this change.
Build:
Unlike the Hackystat build environment some of our projects can be
built within the submodules. Currently, the Drill Down for Build data
does not show the toplevel workspace. Can this be changed as well?
thanks, Aaron
