Ross Patterson writes: > 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
While investigating on this i found out that it seems to be the easiest way to fix the mentioned behavior to pull the RunnableProcess class out of the ProcessExecutor class and also use it in the ProcessMonitor instead of using the Process class directly. If that's not a problem i think i can provide a patch. regards, Daniel
