Hello,
I am running BurnInTest Linux V5.0 (1015) in command line, and my goal is to have the test run 5 cycles of the USB test on the one loopback plug. The following are some of the key settings used in cmdline_config.txt, the full config is attached:
<DutyCycles>
AutoStopMinutes 0
AutoStopCycles 5
USB 100
</DutyCycles>
<USB>
AutoSelectAllUSB
RunUSBBenchmark
USB3Connection Auto
</USB>
It starts the test as expected, running operations on the single USB 3.0 loopback plugged in, but when it reaches 5 cycles, it continues. I let it go for 9 cycles before stopping it. Then, the AutoStopMinutes was changed to 20 and the test was rerun. The test completed 6 cycles and stopped at 20 minutes.
I see another forum post was made in March where a different user had the same issue. A comment was made that a fix would be in the next public release, which in the patch notes appears to be Version 5.0 build 1010 "Fixed issue where USB & network tests did not stop when using cycle count to stop test run." Wondering if the same bug has come back? Or is there another setting in the config I should be looking at?
Thank you,
Parker
I am running BurnInTest Linux V5.0 (1015) in command line, and my goal is to have the test run 5 cycles of the USB test on the one loopback plug. The following are some of the key settings used in cmdline_config.txt, the full config is attached:
<DutyCycles>
AutoStopMinutes 0
AutoStopCycles 5
USB 100
</DutyCycles>
<USB>
AutoSelectAllUSB
RunUSBBenchmark
USB3Connection Auto
</USB>
It starts the test as expected, running operations on the single USB 3.0 loopback plugged in, but when it reaches 5 cycles, it continues. I let it go for 9 cycles before stopping it. Then, the AutoStopMinutes was changed to 20 and the test was rerun. The test completed 6 cycles and stopped at 20 minutes.
I see another forum post was made in March where a different user had the same issue. A comment was made that a fix would be in the next public release, which in the patch notes appears to be Version 5.0 build 1010 "Fixed issue where USB & network tests did not stop when using cycle count to stop test run." Wondering if the same bug has come back? Or is there another setting in the config I should be looking at?
Thank you,
Parker
Comment