Report Steps Missing

[Bob_Y.]

I'm running my sequence from the sequence editor with Single Pass.  I have the report setup for xml as I like the collapsed/expended steps.  When I run a sequence that calls several subsequences, one of them does not add all of its steps to the report.  It adds the call to the subsequence, its header, and the first step.  It shows running in the call to the sequence.  At the completion of the subsequence, that is all that is appended to the report.  I call this sub-sequence from several places and it always results in this report.

I am not sure why a finished report has a running step result and I am not sure why the report does not include all of the steps.  I am pretty sure I must have set something, in that sequence, somewhere, I am just not sure what.  Any ideas?

Thanks,
Bob Young

[Anand_Jain]

Bob

Can you please post a sequence file which shows this problem

Thank you

Anand Jain

National Instruments

[Bob_Y.]

Sure.

The caller is 11.06.01 boot block hold input pin test.seq
and the one that is reported incorrectly is the first subsequence common setup.seq

I am pretty sure my problem is in the caller or in the station.  If I place a different subsequence call to be the first call of the setup, it will be reported wrong instead.  This is very confusing to me.  It happens in a lot of different tests, but they are all modifed clones so it could be an error that has been copied all over.

Thanks for looking into this.
Bob Young

[SercoSteve]

Hi Bob

I can't open your examples (still in the TestStand 3.1 dark ages). 

A quick check however might be to ensure that the Record Results option is selected in your sub sequence calls and/or in the steps within your sub sequences that you aren't getting results for.  To access the Record Results option, right click on the step or sub sequence, select Properties and then the Run Options tab.  Down the bottom of the Run Options tab is a Record Results tick box.  This box will need to be set for results to appear.

Regards

Steve

[RayFarmer]

Hi Bob,

Couldn't see anything obvious, but maybe its related to the relative addressing of the sequence file.

Regards

Ray Farmer