Whamcloud - gitweb
LU-16692 tests: remove force_new_seq from some test suites 33/54433/3
authorLi Dongyang <dongyangli@ddn.com>
Fri, 15 Mar 2024 11:39:30 +0000 (22:39 +1100)
committerOleg Drokin <green@whamcloud.com>
Mon, 8 Apr 2024 15:35:07 +0000 (15:35 +0000)
commit9ef186b71b350127e7cfb67be5729f9e0bd39c79
tree20ed5e0da77c3d41a47a5115d9d6740f1846dcb5
parentf00d2467fc7c5ebd8a313683e039bf945a4b7094
LU-16692 tests: remove force_new_seq from some test suites

force_new_seq was used in some tests to avoid the
situation where the sequence from replay request
could be different than the one osp is at, due to
previous sequence width has been used up.

Now it can be handled so remvoe the force_new_seq
to speed up test runs.
Some force_new_seq are still required to make sure
there are enough objects in the current precreate pool
for the overstriping test cases.

Change-Id: Id1bc6760e721db61c11b1c3d6b2fa82965459728
Signed-off-by: Li Dongyang <dongyangli@ddn.com>
Reviewed-on: https://review.whamcloud.com/c/fs/lustre-release/+/54433
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Reviewed-by: Alex Zhuravlev <bzzz@whamcloud.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>
lustre/tests/replay-dual.sh
lustre/tests/replay-ost-single.sh
lustre/tests/replay-single.sh
lustre/tests/replay-vbr.sh