A syntax-error in one of our tests did not trigger a non-zero exitcode as expected:
Logs from TeamCity:
[12:04:24][Step 3/5] Starting: C:\TeamCity\buildAgent\work\7404058d576e467c\buildframework\Chutzpah\chutzpah.console.exe /path src\JSClient.Tests\spec __/failOnError__ /timeoutMilliseconds 20000
[12:04:24][Step 3/5] in directory: C:\TeamCity\buildAgent\work\7404058d576e467c
[12:04:25][Step 3/5] Chutzpah console test runner (64-bit .NET 4.0.30319.1008)
[12:04:25][Step 3/5] Copyright (C) 2013 Matthew Manela (http://matthewmanela.com).
[12:04:29][Step 3/5]
[12:04:29][Step 3/5] chutzpah.dll: Version __2.5.0.0__
<SNIP>
[12:07:20][JavaScript Tests] Chutzpah Error: C:\TeamCity\buildAgent\work\7404058d576e467c\src\JSClient.Tests\spec\contract_controller_spec.coffee: Error in [JavaScript runtime error]:
[12:07:20][JavaScript Tests] unmatched )
[12:07:20][JavaScript Tests] While Running:C:\TeamCity\buildAgent\work\7404058d576e467c\src\JSClient.Tests\spec\contract_controller_spec.coffee
<SNIP>
[12:09:31][Step 3/5] Process exited with code 0
Comments: using the new showFailureReport flag from v3 fixed my issue - Thanks!
Logs from TeamCity:
[12:04:24][Step 3/5] Starting: C:\TeamCity\buildAgent\work\7404058d576e467c\buildframework\Chutzpah\chutzpah.console.exe /path src\JSClient.Tests\spec __/failOnError__ /timeoutMilliseconds 20000
[12:04:24][Step 3/5] in directory: C:\TeamCity\buildAgent\work\7404058d576e467c
[12:04:25][Step 3/5] Chutzpah console test runner (64-bit .NET 4.0.30319.1008)
[12:04:25][Step 3/5] Copyright (C) 2013 Matthew Manela (http://matthewmanela.com).
[12:04:29][Step 3/5]
[12:04:29][Step 3/5] chutzpah.dll: Version __2.5.0.0__
<SNIP>
[12:07:20][JavaScript Tests] Chutzpah Error: C:\TeamCity\buildAgent\work\7404058d576e467c\src\JSClient.Tests\spec\contract_controller_spec.coffee: Error in [JavaScript runtime error]:
[12:07:20][JavaScript Tests] unmatched )
[12:07:20][JavaScript Tests] While Running:C:\TeamCity\buildAgent\work\7404058d576e467c\src\JSClient.Tests\spec\contract_controller_spec.coffee
<SNIP>
[12:09:31][Step 3/5] Process exited with code 0
Comments: using the new showFailureReport flag from v3 fixed my issue - Thanks!