The behavior is by design to help catch the situation where you might accidentally provide an invalid filter for example.
To work around it in this case, set the MSBuild IgnoreExitCode attribute on the Exec task when calling Gallio.Echo and store the output ExitCode value into a property called ExitCode (or whatever). Then you can follow the call to Exec with <Error Text="Tests failed!" Condition="'$(ExitCode)'!='0' and '$(ExitCode)'!='16'" /> Aside: I recommend using the Gallio custom task in Gallio.MSBuildTasks to run tests from MSBuild instead of using Echo directly. Jeff -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dev Mike Sent: Monday, June 01, 2009 8:06 AM To: MbUnit.User Subject: MbUnit Gallio.Echo.exe exit codes Greetings, I am running Gallio.Echo.exe with the following command line: (roughly) Gallio.Echo.exe C:\TestAssembly\Tests.dll /v:Normal /rt:text /rd:C: \TestResults /filter:CategoryName:foo /rnf:Tests The important part is that I am filtering my test assemblies on 'CategoryName', our build process combs our directory structure looking for test assemblies, and if it finds one it runs it with the above filter, however as some of our test assemblies don't contain the filtered category name (foo in this case), the test runner is returning with exit code 16. As I am running this through an MSBuild shell, MSBuild evaluates exit code 16 as failure. Is there anyway I can refine my filter so that it doesn't return 16, or is there some solution to this problem that I am not seeing currently. Thanks in advance for any help with this. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
