Hi
fixed in the latest build. Someone had hardcoded that string in the log :-( with kind regards Ruben Willems On Mon, Oct 12, 2009 at 9:41 PM, Ruben Willems <[email protected]>wrote: > Hi > > I'm now also setting up a 1.5 > did not have the time before :-( > > and I see it also, very annotying item, sorry for this > tracking it down now ... > > > with kind regards > Ruben Willems > > > On Mon, Oct 12, 2009 at 9:39 PM, Carl Cerecke <[email protected]>wrote: > >> >> I am seeing this also. I haven't had time to investigate yet. >> >> Yes, the final build state is correct ("Success"), but for each task >> there is a "Task execution failed" entry in the log. >> >> Cheers, >> Carl. >> >> On Mon, Oct 12, 2009 at 11:32 PM, Ruben Willems <[email protected]> >> wrote: >> > Hi >> > >> > >> > this sounds like a new bug :-( >> > So you mean that the final build state is OK : as it should, >> > but in the log you see several 'Task Execution Failed' >> > >> > can you post the batch file you're using, or one with the similar >> result? >> > >> > I suspect that these errors come from sub-tasks that are introduced into >> > CCNet 1.5. >> > >> > >> > with kind regards >> > Ruben Willems >> > >> > On Mon, Oct 12, 2009 at 12:13 PM, Sam Lai <[email protected]> wrote: >> >> >> >> 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:\>setlocal</message> >> >> <message>C:\>echo "BCS10112009100024" </message> >> >> <message>C:\>endlocal</message> >> >> <message>C:\>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 >> > >> > >> >> >> >> -- >> Carl Cerecke >> GeoBase Senior Software Engineer – Telogis Research >> www.telogis.com www.telogis.co.nz >> +1 949 625-4115 ext. 208 (USA) +64 3 339 2825 ext. 208 (NZ) >> -- >> This e-mail, and any attachments, is intended only for use by the >> addressee(s) named herein and may contain legally privileged and/or >> confidential information. It is the property of Telogis. If you are >> not the intended recipient of this e-mail, you are hereby notified >> that any dissemination, distribution or copying of this e-mail, any >> attachments thereto, and use of the information contained, is strictly >> prohibited. If you have received this e-mail in error, please notify >> the sender and permanently delete the original and any copy there of. >> > >
