Strange. The analysis page does show that you have a bunch of commits.
I'll check why the final conclusion says "no commit".
Note that you tested everything on your local computer before committing
changes (fully tested). The failure is in PRI, but you did not commit
any thing in PRI. The current AI cannot trace the culprit back to you.
I am thinking whether this provides the motivation for us to use
dependency data.
Cheers,
Cedric
Philip Johnson wrote:
Cedric,
I did commit this file, and so I should have been detected as the
culprit. (And I also did a freshStart all.junit, so I'm not sure why
it failed!)
Could you investigate why the analysis came to the wrong conclusion?
I will fix the failure.
Cheers,
Philip
--On Thursday, January 26, 2006 6:00 AM -1000 Hackystat Administrator
<[EMAIL PROTECTED]> wrote:
The following alert(s) were triggered today:
* Build analysis for project Hackystat-7:
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
