That is also what happened with the build server (sort of). After a nightly build is done, the binaries are updated (on the build server). That means the next run use the latest binaries from the night before. Now, this should not be a problem, as we run the tests with this version of the binaries, but apparently there are some issues. The latest problem (from 3 days ago) was that the settings file was not be read from the correct place (because of the shadowcopy files), and failing when it wasn't found.
The other problem is that draco isn't correctly detecting the failure. This has to do with reading the exit code correctly from nant. I believe that this problems has now been fixed in draco cvs tree and requires me to rebuild and deploy. I will do this later today. ----- Original Message ----- From: "Ian MacLean" <[EMAIL PROTECTED]> > What happened is that Scott checked in new copies of the biniaries in > nant\bin. Those binaries had your change. So it wasn;t until someone > built Nant with those binaries that a failure occurred ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
