On Fri, Aug 29, 2008 at 08:47, JDAVIDI <[EMAIL PROTECTED]> wrote: > Below is a log snippet from when I issued an Abort Build to when it > aborted. > > I was expecting the project to remain in its previous 'successful' > state (akin to killing the ccnet.exe console), but instead the project > flipped to a failure state and ended up emailing the engineers on the > last modification list with no errors listed or any indication of the > abort. > > Is this behavior by design, or did it happen to be caused by where the > the project was (mid-Visual Studio build) when the abort was > processed? >
I wouldn't go so far as to say it's by design, but it certainly is the way CCNet works. The build has already started and must have a final status, and builds either succeed or fail - there is no in-between state. I'll grant that the abort code should include an error to the effect that the build failed because it was aborted, rather than just being quiet. Ross
