Failure step ignoring subroutine grouping

[ebriggs]

We just upgraded from Visual Build 5.7 to Visual Build 7.2. Now we're having a problem when a step fails. The first step in our list of "Failure Steps" calls a subroutine that contains a single step. For some reason, after this step executes it doesn't go back to the "Failure Steps" tab to continue executing the next failure step. Instead it continues on with the *next* subroutine on the "Subroutine Steps" tab. This is causing a loop to occur because that subroutine fails (because it's not supposed to be randomly executed and requires the caller to pass a parameter to it), which causes the Failure Steps to execute, which calls the subroutine mentioned before, etc...

Has anyone else seen this? This was working fine in version 5.7; I haven't changed anything.

Thanks!
Emily

[kinook]

This appears to be a bug in v6.0 and later that only occurs when building all failure steps and the first failure step calls a subroutine. The following workarounds can be used:

1) Add a step before the Subroutine Call step (i.e., a Group or Log Message step) so that the Subroutine Call step is not the first failure step.

or

2) Add an Exit step at the end of the subroutine that is called from the failure steps.

http://www.kinook.com/VisBuildPro/Manual/exitaction.htm

[ebriggs]

Thank you! Any idea when this will be fixed?

~ Emily

[kinook]

Not sure. It is a fairly minor bug with 2 simple workarounds, and you were the first to encounter it in nearly 4 years of existence...