My hypothesis:
(1) Temp22303.png is generated by hackyReport module, the file is subject to garbage collection.
(2) When hackystat starts, it spawns a temporary file reaper thread, which wakes up at certain intervals (maybe one hour).
(3) At the time ant trys to copy files to a differnt location (build.xml:1333), tomcat still runs, so does the file reaper thread. It could be: (a) Ant remembers the list of files to copy. (b) The reaper deletes the temporary. (c) Ant tries to copy the files it previous remembered.
This is possible since building ALL on hackydev takes sometimes more than one hour.
Of couse, my hypothesis is pending validation.
Cheers,
Cedric
Philip Johnson wrote:
Strange error. Cedric, have any ideas?
Build Failed - C:\CruiseControls\instance-ALL\hacky\hackyBuild\build.xml:1333: Failed to copy C:\CruiseControls\instance-ALL\hacky\hackyBuild\build\war\tmp\testdataset\Temp22303.png
to C:\CruiseControls\instance-ALL\hacky\hackyBuild\build\dist\stagearea\hackystat-all-6.5.503\hackyBuild\build\war\tmp\testdataset\Temp22303.png
due to C:\CruiseControls\instance-ALL\hacky\hackyBuild\build\war\tmp\testdataset\Temp22303.png
(The system cannot find the file specified).
--On Tuesday, May 03, 2005 3:35 AM -1000 [EMAIL PROTECTED] wrote:
Hackystat build (configuration Hackystat-ALL) failed. Build report is available at http://xenia.ics.hawaii.edu/hackyDevSite/configurationBuildReport.do?year=2005&month=5&;
day=3&configuration=Hackystat-ALL Build Time Stamp: Tue May 03 03:35:30 HST 2005
