Only Log results from last loop iteration on failure.

[svacek]

Hoping someone can help me figure this out....

I'm running a 24 hr burn-in on my UUT.  Current sequence file executes the setup, then calls a subsequence that contains various UUT reads and data measurements(26 different reads).  This subsequence executes in a loop for approx 12hours. After 12 hours, I then execute a few steps to change UUT configuration before entering the second half of the burn-in test...which is essentially the same looped sequence call as executed above.

Obviously, logging 24 hours of looped data reads is going to result in an enormous log file. Currently using result filtering to limit data loging to Failed steps only, which is great as it keeps log file size to a minimum.  However, for debugging purposes, it would be extremely useful to be able to log all of the results from the previous loop iteration.

Any thoughts?

Thanks

[WireWeaver · Accepted solution]

Instead of logging the data to a report with the step.results container, you could try logging the debug info you're looking for to an outputrecordstream and writing it to CSV. (This functionality was added in TestStand 2017):

https://www.ni.com/docs/en-US/bundle/teststand-api-reference/page/tsref/the-inputrecordstream-and-ou...