[Mono-bugs] [Bug 82796][Nor] New - System.Diagnostics.Process.ExitCode always returns 0 for NAnt

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Sep 11 03:12:26 EDT 2007

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by skolima at gmail.com.


--- shadow/82796	2007-09-11 03:12:26.000000000 -0400
+++ shadow/82796.tmp.18894	2007-09-11 03:12:26.000000000 -0400
@@ -0,0 +1,39 @@
+Bug#: 82796
+Product: Mono: Class Libraries
+Version: 1.2
+OS: other
+OS Details: Gentoo linux, mono 1.2.5 and svn-head
+Status: NEW   
+Priority: Normal
+Component: CORLIB
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: skolima at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: System.Diagnostics.Process.ExitCode always returns 0 for NAnt
+Description of Problem:
+I am running CruiseControl.Net on a linux box. The problem is that al
+builds are reported as successful. I have pinned the problem down to
+Process.ExitCode always returning ExitCode 0 for NAnt execution. The
+process returns correct values for other programs (e.g. `true`, `false`).
+Also, when NAnt is run in shell, the exit code is set as expected (checked
+with `echo $?`);
+Steps to reproduce the problem:
+1. With NAnt installed, run the attached sample in a directory without
+.build file.
+2. NAnt will fail.
+Actual Results:
+Process.ExitCode returns 0
+Expected Results:
+Process.ExitCode returns 1
+How often does this happen? 
+Always. I also tried various combinations of bypassing the wrapper scripts,
+but did not manage to get the ExitCode.

More information about the mono-bugs mailing list