Hey Guys,
I have a couple of comments about the build failures associated with
hackyInstaller.
1) I think the test cases download jar files from
http://hackystat.ics.hawaii.edu instead of http://localhost:8080 (or what
ever is set in the properties).
2) I noticed that my sensor.properties file is "touched" by hackyInstaller
testcases. Does that mean it could potentially change it? Or that it is
actually being used in the test cases? In either case, that is probably bad.
Side Note:
I noticed hackyinstaller.xml file, which contains ANT_HOME. It showed an
Ant version I don't use. I upgraded ANT and changed my ANT_HOME a while
ago in my environment variables. So, if I didn't know to check my ANT HOME
in hackyInstaller then my sensors could be broken. Anyway, the point is
that could it be possible to use the ANT_HOME in my ENV instead of manually
setting it. Or possibly check the value to see if they match.
I suppose the good thing is that after fixing my ANT_HOME value in
hackyinstaller.xml and running the test cases, TestBuildSensorInstaller
continued to fail.
thanks, aaron
At 09:19 AM 9/2/2005, you wrote:
I have no idea what is going on but I'm working on the randomly failing
Test*SensorInstaller
test cases. I haven't changed them since the integration and they are
doing strange things
now. I am going to try to redo a few things and then commit
it. Hopefully I can get the new
test cases in by tonight. Sorry for all the build failures...
~Julie
----- Original Message -----
From: Qin Zhang <[EMAIL PROTECTED]>
Date: Friday, September 2, 2005 3:51 am
Subject: [HACKYSTAT-DEV-L] Hackystat-ALL Build Failed
> Hackystat build (configuration Hackystat-ALL) failed.
> Build report is available at
> http://xenia.ics.hawaii.edu/hackyDevSite/configurationBuildReport.do?
year=2005&month=9&day=2&configuration=Hackystat-ALL
> Build Time Stamp: Fri Sep 02 03:51:31 HST 2005
>
