The title of this explains the issue BurnInTest 9.1 Scripts continue to run after pressing the stop button, this behavior was not present in 9.0.
This is actually stopping us from using 9.1 because the only way to stop the testing is to close BurnInTest.
I was able to replicate this behavior on build 1000 & 1002
See example script below
LOG "START OF TESTING CYCLE"
LOOP 24
{
LOG "HOT CYCLE"
LOAD "DEFAULT.bitcfg"
SETDURATION 50
RUN CONFIG
LOG "COLD CYCLE"
SETDURATION 10
RUN NETWORK
}
LOAD "DEFAULT.bitcfg"
SETDURATION 5
RUN CONFIG
LOG "END OF TESTING CYCLE"
This is actually stopping us from using 9.1 because the only way to stop the testing is to close BurnInTest.
I was able to replicate this behavior on build 1000 & 1002
See example script below
LOG "START OF TESTING CYCLE"
LOOP 24
{
LOG "HOT CYCLE"
LOAD "DEFAULT.bitcfg"
SETDURATION 50
RUN CONFIG
LOG "COLD CYCLE"
SETDURATION 10
RUN NETWORK
}
LOAD "DEFAULT.bitcfg"
SETDURATION 5
RUN CONFIG
LOG "END OF TESTING CYCLE"
Comment