Test result stuck on a runing state

[sklod]

Hi,

We had a problem of test results getting stuck on a runing state despite testing continuing in production.

 

I had to restart the sequence on both computer that got stuck. 

Anyone have a clue of why this happened or a hint to help me find out the why?

[alex_weaver]

Hi sklod,

A few questions:

- Are you using the TestStand plugin?

- What version of Test Module and SystemLink Client are you using?

- Is something unusual happening on the tester, or is it just randomly dropping out for seemingly no reason? This can happen if the tester suddenly stops running.

- Is it just the result that was stuck in running? Did any steps show up?

- Do you have store & forward enabled? If so, it's possible that you had a network outage and the last half of the sequence was stored locally.

[sklod]

Hi, 

Thanks for the reply.

-I am using the teststand plugin

-I am using the version bellow

-Nothing happened on the tester, Teststand continued to test without showing any error but not saving results on SystemLink

-Yes it was only the running that showed up all the step were there but they were no result saved between the time the problem occured and the time i restarted teststand despite of product being tested with no error.

-We aren't enabling the store and forward since it doesn't work properly for us (I need to find the time to check that problem and open a new post).

[HVW]

Hi Alex, any clue on that?

[alex_weaver]

What process model are you using? Is it a modified one, or one that comes with TestStand?

The process model passes the final state of the execution to each process model plugin via a parameter to the "Model Plugin - UUT Done" callback called "MainSequenceResult." SystemLink then parses this state object and updates the result serverside. After placing a breakpoint there and simulating various types of issues (e.g. connection failure), I still consistently got a TS error dialog as long as store & forward was disabled. However, in every case, the final state on the TS-generated report was still "Passed" since the generated error happened after the main body of the execution. Is it possible that something is suppressing dialogs or otherwise handling/consuming TS execution errors?

When you navigate to Configure -> Result Processing and open the options for the SystemLink plugin, what is the configuration of all the checkboxes?

Would you able to send me log data about the system, so that I can look deeper into this specific environment? The two main pieces I'd be interested in are:

1. On the server, open "NI SystemLink Server Configuration" and under "Troubleshooting," the contents of the technical support report.

2. On a tester where this problem has occurred in the past, the contents of C:\ProgramData\National Instruments\Skyline\Data\Store.

My email is alex.weaver@ni.com. Keep in mind that some of the files that I listed above may contain result data, so I do understand if they can't be sent.

[HVW]

Hi Alex,

Sorry for the delay.

We're currently using the SequentialModel.seq process model coming with TS.

We're using a MainSequence that's calling a sub sequence. We have the:

- ReportOptions : to set the format of our test file, and to able/disable reports generation (it's always set when we're producing and when we have that problem)

- SequenceFilePostResultListEntry callback is overrided to remove skipped test from the results

for the TS popup it could be yes I guess, we're setting the following settings in the StationOptions:

and here is our configuration for the SystemLink plugin in TS

We had the problem yesterday and we lost some data, since it's test product data I will continue by email with you and sklod