On Thu, Jul 21, 2016 at 06:41:00PM +0800, Eryu Guan wrote: > On Thu, Jul 21, 2016 at 03:30:25PM +0800, Wang Xiaoguang wrote: > > + > > +run_time=$((180 * $TIME_FACTOR)) > > 180s is too long time, I can reproduce it in around 10s on my test vm, > just loop for 100 times for each operation (pwrite and falloc) Or simply do: run_time=$((20 * $TIME_FACTOR * $TIME_FACTOR)) So that the time factor scales up quickly when you want to run long running tests. > > --- a/tests/generic/group > > +++ b/tests/generic/group > > @@ -373,3 +373,4 @@ > > 368 auto quick richacl > > 369 auto quick richacl > > 370 auto quick richacl > > +371 auto enospc prealloc stress > > So we can add 'quick' group and remove 'stress'. I'd leave the test in stress if we can run it based on time as per my above suggestion. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
