Build 1689 Stages after Unit Tests ignore stage gate settings

When I create a stage that includes nunit tests, it doesn't matter what sort of stage gate options I set or if there are no options, it will not execute the next stage. I tried to set a series of stage gate settings

a) No criteria

b) Setting the unit tests passed greater than or equal to a known value that should pass.

c) setting the unit tests to allow failures.

Couldn't get anything to allow the next stage to run.  In this case I had a series of non fatal unit test failures (environment issues).

Attachment unavailable

What actually happens when the build stops. Do you see the stage gate message about metrics or something else?

The build just seems to skip the 3rd and final stage with the last timeline log entry “Build Failed” (within the Unit test stage). There is nothing in any of my tests reporting on the reason behind the failure. It looks like nunit tests failure are a hard coded failure point within the Continua build process.

Build failed 2 hours, 8 minutes ago 0 milliseconds
Stage executing 2 hours, 8 minutes ago 203 milliseconds Stage done on agent ‘jdbne01’.
Stage executing 2 hours, 8 minutes ago 250 milliseconds Syncing workspace from agent ‘jdbne01’ to server
Stage executing 2 hours, 9 minutes ago 1 minute Executing stage on agent jdbne01
Stage initialising 2 hours, 9 minutes ago 1 second Initialising workspace on agent ‘jdbne01’
Stage initialising 2 hours, 9 minutes ago 125 milliseconds Sending stage ‘Test’ to agent ‘Test’
Stage initialising 2 hours, 9 minutes ago 173 milliseconds Initialising Stage…
Stage ready 2 hours, 9 minutes ago 93 milliseconds Agent ‘jdbne01’ reserved and license allocated for stage ‘Test’
Stage awaiting agent 2 hours, 9 minutes ago 578 milliseconds Allocating agent
Stage executing 2 hours, 9 minutes ago 218 milliseconds Stage done on agent ‘jdbne01’.
Stage executing 2 hours, 9 minutes ago 312 milliseconds Syncing workspace from agent ‘jdbne01’ to server
Stage executing 2 hours, 9 minutes ago 1 second Executing stage on agent jdbne01
Stage initialising 2 hours, 9 minutes ago 1 second Initialising workspace on agent ‘jdbne01’
Stage initialising 2 hours, 9 minutes ago 93 milliseconds Sending stage ‘Compile’ to agent ‘Compile’
Stage initialising 2 hours, 9 minutes ago 171 milliseconds Initialising Stage…
Stage ready 2 hours, 9 minutes ago 46 milliseconds Agent ‘jdbne01’ reserved and license allocated for stage ‘Compile’
Stage awaiting agent 2 hours, 9 minutes ago 156 milliseconds Allocating agent
Build started 2 hours, 9 minutes ago 14 milliseconds Build started
Build starting 2 hours, 9 minutes ago 126 milliseconds
Build queued 2 hours, 9 minutes ago 15 milliseconds Starting build.
Build queued 2 hours, 9 minutes ago 187 milliseconds Checking configuration conditions.
Build queued 2 hours, 9 minutes ago 15 milliseconds Checking configuration discard conditions
Build queued 2 hours, 9 minutes ago 46 milliseconds
Build initialising 2 hours, 9 minutes ago 15 milliseconds Queueing Build
Build initialising 2 hours, 9 minutes ago 15 milliseconds Creating build Stages.
Build initialising 2 hours, 9 minutes ago 15 milliseconds Creating build log file.
Build initialising 2 hours, 9 minutes ago 46 milliseconds Initializing build Workspace on Server.
Build initialising 2 hours, 9 minutes ago 15 milliseconds Initializing build on Server.
Build initialising 2 hours, 9 minutes ago 46 milliseconds Associating changesets with the build.
Build initialising 2 hours, 9 minutes ago 13 seconds [Repository Monitor] Waiting for repository ‘JD-Data-Kiln’ to be checked.
Build initialising 2 hours, 9 minutes ago 15 milliseconds Waiting for Repositories to be checked

To put this in context I’m working on mixed architecture unit testing. Where OS is x64 or x86 and the application is x64 or x86 and automation of other products that might be mixed architectures (think MS Office data drivers). So it would be ok to build a x86 edition if those unit tests passed etc.

[code] Environment.Is64BitProcess [/code]

the action defaults to fail if any unit tests fail, however you can turn off that option if desired.

I've tried with and without the Nunit configuration Check Box "Fail action if any tests fail", both block the stage gate evaluation. Is this the setting your referring too?

Here are my settings for your review.

Attachment unavailable

Yes, that’s the option. I thought you were concerned with the build failing. If that option is off, and you remove the conditions from the stage gate after the current stage, does that stop the build? That doesn’t sound right… will look into it if that’s what you are seeing?