05-07-2008 01:39 PM
05-07-2008 03:32 PM
05-07-2008 04:01 PM - edited 05-07-2008 04:02 PM
05-07-2008 05:42 PM
08-15-2012 07:19 PM
Can you guys explain a little more what this is actually doing? The Help file is mildly cryptic and even what you guys are saying here aren't helping. What I've done is called launched a new Execution, from there I have several Subsequences launched as Threads, Don't wait to Complete any of them, and I'm experimenting with setting the Ignore Termination.
This is all being run from the Sequence Editor.
To me...the way I expected this to work when I first saw the option was that any Terminate button clicks while viewing this Execution or any Terminate All clicks and these Threads would continue merily running, not bothering to Terminate. It seems like from reading these comments here that it has nothing at all to do with this and only effects what the report will show. Is this true?
08-16-2012 10:16 AM - edited 08-16-2012 10:16 AM
That is not what ignore termination does. It is for regular (not new-thread or new-execution) sequence calls. What it does is cancel the termination at the point of the sequence call. Termination still happens in the subsequence, but when it gets back to the sequence call it is effectively cancelled at that point and the status of the execution is no longer terminated.
There is a new API that was added to TestStand 2012 (which is now available on our website) that does something more like what you are asking. Here is the documentation for that new API:
Use the following constants with this data type:
ThreadTerminationOption_Never–(Value: 2) Specifies that a thread does not stop when its execution terminates. The thread must end on its own accord before its execution can end. Use this value to protect a thread so the thread does not stop and can complete its work even if its execution attempts to terminate.
ThreadTerminationOption_Normal–(Value: 0) Specifies that a thread stops when its execution terminates.
ThreadTerminationOption_Prompt–(Value: 1) Specifies that a thread does not stop when its execution terminates unless you set the Execution.OverrideNonTerminatableThreads property. If an execution attempts to terminate and the execution is running only threads that specify this option, the execution sends the UIMsg_NonTerminatableThreadsArePreventingTerminati
Specifies the behavior of a thread when its execution attempts to terminate. This property does not inhibit aborting. The default value is ThreadTerminationOptions_Normal.
Hope this helps,
08-16-2012 10:50 AM
Would you have any trepidation in upgrading from 2010 SP1 up to 2012 or expect any real problems to crop up from doing so? I suppose its easy enough to put 2012 on the same box and just try it out? I'm just wondering about the behind the scenes stuff, libraries, APIs, etc stepping on each others toes and causing some real headaches.
08-17-2012 11:06 AM
The biggest changes for 2012 were to the process models. Though you can still use models based on the old process models if you like (you'd just need to copy all of the files for the models you are using to the corresponding location in the public directory). Generally, newer versions of TestStand should be backwards compatible with previous versions.