Error generating ATML report with sequence call

[Alex_Haak]

When my main squence calls another sequence (which passes), the ATML report generator produces an error. This happens in both atml 2.02 and 5.00. The error message I get is:

   An exception occurred inside of the call to .NET member 'GenerateReport':
System.Runtime.InteropServices.COMException (0xFFFFBC6B): Index out of range.
   at NationalInstruments.TestStand.Interop.API.ReportSections.get_Item(Object index)
   at NIOTFReportGenerator.CollectionStepResult.UpdateExisting(IStepResult updatedStepResultI, Boolean usingConserveMemory, ReportFileStream& tempFileStream)
   at NIOTFReportGenerator.ChildStepResults.ProcessNewStepResults(Hashtable& newThreadSeqCallResults, Boolean usingConserveMemory, ReportFileStream& tempFileStream, String[] reportSnippets, Int64 offsetAdjustment)
   at NIOTFReportGenerator.OTFRptGenerator.GenerateReport(SequenceContext sequenceContext, String inputReportHeader, String inputReportFooter, ReportSection& mainSequenceReportSection, String& errorMessage, Double& errorCode, Boolean& errorOccurred)

-17500; Operation Failed.

Step 'Generate Report' of sequence 'ProcessOTFStepResults' in 'ReportGen_ATML.seq'

I need to really use ATML so that i can filter results aswell.

Surely someone else has had the same problem.

Thanks

[Anand_Jain]

Can you please post an sample sequence file which can be used to reproduce the issue.

Thank you
Anan Jain
National Instruments

[Alex_Haak]

So i think i have fixed/avoided the problem.

The problem was that i was filtering the results i was recording to exclude any passes. This meant that a sequence that passed was trying to be recorded but couldnt because i had disabled it. It seems this is a fault from teststand, as it should have just not recorded the sequences result. As for whether the contents of that sequence would be recorded is probably where the problem stems from. 

If someone else could verify this then I will report it as an error. Simply create a sequence file that makes a call to another sequence. Make sure result filtering is enabled to exclude "Passed" results.

To avoid the problem I simply added an extra result type so that i didnt have to exclude passed results.

[Anand_Jain]

Alex, 

I have reproduced this issue and yes, that is a bug in TestStand on-the-fly report generator.

I will report this bug internally and it will be fixed in a future version of TestStand. 

Regards

Anand Jain

National Instruments

[Alex_Haak]

Ah ok, thanks for your help.

Alex

[awilke_QTC]

Has this bug ever been fixed? I'm using TestStand 2013 and I'm still having the same issue in my sequence.

[Anand_Jain]

awilke_QTC, 

Unfortunately, this issue has not yet been fixed and will still occur in TS 2013. I will bump up the priority of this issue. 

Did you try the workaround described earlier in the post?

Regards

Anand Jain

National Instruments

[awilke_QTC]

Unfortunately the workaround doesn't work for my needs. I need to have "Passed" results excluded from the report and I must use on-the-fly reporting.

[Al.B]

Hi awilke_QTC,

You can also work around the issue by excluding sequence call steps from the report in addition to passed results, using a filtering expression like this:

Result.Status != "Passed" && Result.TS.StepType != "SequenceCall"

Would this alternative work for your use case?

[swiker87]

Has this bug been fixed? im encountering it and i need on the fly reporting to solve a memory leak issue