I have a rarely occurring "long delay" issue when using a resource via network. It usually happens in the 8-15 hours range but sometimes never. It usually recover after a few minutes (of a transactions that takes less than a second).
I wish I could loop my tests all night, but be certain it stops in the morning to free the resources. If I do a "CTRL-C" I miss the final report.
- Using the repeat I have to guesstimate how many loops I will need for H hours and hope the error will occur at least once in the time-frame.
Using the 'run-untill-failure' is not great either since the problem may not occur at all. And I want the test loop to continue to get statistics on recovery time.
Not a big priority, but a nice to have.
Thanks for the great work.
I have a rarely occurring "long delay" issue when using a resource via network. It usually happens in the 8-15 hours range but sometimes never. It usually recover after a few minutes (of a transactions that takes less than a second).
I wish I could loop my tests all night, but be certain it stops in the morning to free the resources. If I do a "CTRL-C" I miss the final report.
Using the 'run-untill-failure' is not great either since the problem may not occur at all. And I want the test loop to continue to get statistics on recovery time.
Not a big priority, but a nice to have.
Thanks for the great work.