The changes to the UnitTest SDT API caused compilation failures in
hackyApp_Pri and hackyApp_CGQM.
I think Hongbing was doing this evolution, so please fix these ripple
effects.
In general, when doing evolution, you'll probably need to run a complete
build and test once before committing your changes to smoke out these kinds
of problems.
Cedric: for your qualitative analysis purposes, the build analysis didn't
catch this, but it wasn't a 'valid' integration-time failure (developers
should now know to do a complete build and test when doing evolution.)
Cheers,
Philip
--On Thursday, April 6, 2006 6:00 AM -1000 Hackystat Administrator
<[EMAIL PROTECTED]> wrote:
Integration build for Hackystat-7 project on 06-Apr-2006 FAILED.
Module: hackyApp_Pri
Failure Types: Compilation
Plausible Culprit: Unknown
How culprit is identified: Build failure reason is unclear, and no one
has made any commit in hackyApp_Pri. Perhaps hackystat sensor data is
incomplete, or it is caused by external error on the integration build
box. Failure Messages:
*
C:\HackystatSource\hackyApp_Pri\src\org\hackystat\app\pri\model\workspace
\measures\helper\WorkspacePriUnitTestResultHelper.java::96::cannot find
symbol *
C:\HackystatSource\hackyApp_Pri\src\org\hackystat\app\pri\model\workspace
\measures\helper\WorkspacePriUnitTestResultHelper.java::120::cannot find
symbol
