To prevent system live-lock with faulty configuration, we need to add timeout as a safety measure. Currently our longest test used about 23 minutes for swap_mutex with 200+ hyper-threads system, therefore we chose 30 minutes as the default sh timeout value. We can easily increase this value if future system has more cores and slower.
This parameter doesn't change successful test case's running time. Because this value should not be changed very often, therefore we used an internal value instead of a yaml config parameter.
To prevent system live-lock with faulty configuration, we need to add timeout as a safety measure. Currently our longest test used about 23 minutes for swap_mutex with 200+ hyper-threads system, therefore we chose 30 minutes as the default sh timeout value. We can easily increase this value if future system has more cores and slower.
This parameter doesn't change successful test case's running time. Because this value should not be changed very often, therefore we used an internal value instead of a yaml config parameter.