NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Analysis errors during deployment build

Solved!
Go to solution

Ok,

 

I have been rrting to figure this one out for hours.....but I just don't get it.

 

I am trying to created a build from my TestStand project. However, I get the warnings listed below when doing the analysis. This also happens when I try using the stock parallel model too.

 

Any thoughts to what is causing this and how to correct it?

 

Thanks,

Ryan

 

 

+++++++++++++++++++++++++++++++++++++++
Starting Analysis
Processing Workspace...
Workspace Processed
Finished Analysis
---------------------------------------
Warning: You may need to add any sequence file(s) referenced by the following expression(s):
"reportgen_" + RunState.Root.Parameters.ModelData.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'SequenceFilePostResultListEntry', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'
"reportgen_" + RunState.Root.Parameters.ModelData.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'ProcessModelPostResultListEntry', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'
"ReportGen_" + Parameters.ReportOptions.ReportStyle + ".seq" in step 'Set ReportOptions based on ReportStyle', sequence 'Get Report Options', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Footer', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Header', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Body (Sequence)', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'
"ReportGen_" + Parameters.ReportOptions.ReportStyle + ".seq" in step 'Get Report based on ReportStyle', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Set Report Disabled Message', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Single Pass -- Test Socket Entry Point', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Test UUTs -- Test Socket Entry Point', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'
Step 'Call Requested Sequence', sequence 'ProcessDialogRequests', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'
RunState.ProcessModelClient in step 'Create Test Socket Execution', sequence 'Initialize TestSocket', sequence file 'C:\Program Files\National Instruments\TestStand 4.2.1\Components\Models\TestStandModels\PROG_ParallelModel.seq'

0 Kudos
Message 1 of 2
(3,103 Views)
Solution
Accepted by topic author SimpleJack

This is just a warning letting you know that a sequence file is called by expression.  The deployment utility cannot determine what sequence file will be called, so it warns you to let you know to make sure you include it.  In this case, all of the reportgen_xxx.seq files need to be included.  You cannot make this message go away without hardcoding sequence file names.  There is nothing wrong with getting this warning as long as you make sure you include everything it might call.

0 Kudos
Message 2 of 2
(3,087 Views)