The build analysis is correct, but it should read
Build failure reason is unclear, and no one has made any commit *in
hackyApp_Pri.*
instead of
Build failure reason is unclear, and no one has made any commit.
I'll log this in Jira, and try to make dependency sensor work again.
Cheers,
Cedric
Philip Johnson wrote:
--On Thursday, January 26, 2006 6:00 AM -1000 Hackystat Administrator
<[EMAIL PROTECTED]> wrote:
Integration build for Hackystat-7 project on 26-Jan-2006 FAILED.
Module: hackyApp_Pri
Failure Types: JUnit
Plausible Culprit: Unknown
How culprit is identified: Build failure reason is unclear, and no
one has made any
commit. Perhaps hackystat sensor data is incomplete, or it is caused
by external error
on the integration build box. Failure Messages:
*
org.hackystat.app.pri.model.workspace.measures.TestWorkspacePriFileMetric
OK, I've got some news on this front:
(a) I just committed a fix to hackySdt_FileMetric to solve this build
failure.
(b) It turns out that I was confusing hackyApp_PrjSize (for which I
did commit changes) with hackyApp_Pri (for which I apparently did not
commit changes, at least for the past five days). I really did think
I did something to hackyApp_Pri, but I guess I didn't. So, the build
analysis did as well as it could do under the circumstances; it was a
classic ripple effect.
(c) Aaron's unit tests for hackyApp_Pri uncovered a subtle bug in my
FileMetric evolution code. Yeah! Hooray for test cases!
Cheers,
Philip
