Dear all,

  I have just updated my servers to ccnet 1.5 and found there was a
quite bugging problem. The exec tasks keep logging "Task Execution
Failed" no matter there are real errors or not.

The logging is as follow

2009-10-12 16:21:54,682 [BOUNDSCHECKER TEST SPECIAL START:INFO] Task
execution failed
2009-10-12 16:21:54,682 [BOUNDSCHECKER TEST SPECIAL START:INFO] Task
output:
<buildresults>
  <message>C:\&gt;setlocal</message>
  <message>C:\&gt;echo "BCS10112009100024" </message>
  <message>C:\&gt;endlocal</message>
  <message>C:\&gt;exit</message>
</buildresults>

I was running a command batch file.
The fortunate thing is, the task does not really fail and the
integration continues.
Moreover,  when there are real errors, it abort the integration.
However, it is still quite confusing and annoying for me to keep
seeing this message.

I have tried a lot of different things, like adding all
successExitCodes, adding EXIT 0 explicitly in batch,  making all a
empty batch etc, turning off TRACE level, but nothing works.

I am using .net framework 2.0 in Windows XP
My question is, is this a known bug or just that i missed out
something ?
Please help!

Thanks
Sam

Reply via email to