@@ -9,7 +9,7 @@
004 auto rw metadata
005 auto defrag
006 auto quick
-007 auto rw metadata send
+007 auto quick rw metadata send
008 auto quick send
009 auto quick subvol
010 auto quick defrag
@@ -52,7 +52,7 @@
047 auto quick send
048 auto quick
049 auto quick
-050 auto send
+050 auto quick send
051 auto quick send
052 auto quick clone
053 auto quick send
@@ -102,8 +102,8 @@
097 auto quick send clone
098 auto quick metadata clone
099 auto quick qgroup
-100 auto quick replace
-101 auto quick replace
+100 auto replace
+101 auto replace
102 auto quick metadata enospc
103 auto quick clone compress
104 auto qgroup
Update the following quick/auto tag based on their execution time 007 050 100 101 Two systems are used to determine their execution time. One is backed by an SATA spinning rust, whose maximum R/W speed is about 100MB/s, modern desktop performance. (VM1) Another one is a VM inside a openstack pool, with stronger CPU and memory performance along with high latency storage. Maximum R/W speed is around 150MB/s, latency is much higher than normal HDD though. (VM2) The 'quick' standard is a little more restrict, only when both systems pass the test within 30s(+/- 10%), while 'auto' is less restrict, any system can pass within 5min(+/- 10%) will still stay in 'auto' group. Other test cases don't fit both standards on both systems will not be modified. Execution time result: (Unit: seconds) ------------------------------------------------------ Test case No. | VM1 | VM2 | Modification | ------------------------------------------------------ 007 | 4 | 2 | +quick | 050 | 4 | 13 | +quick | 100 | 57 | 151 | -quick | 101 | 45 | 59 | -quick | ------------------------------------------------------ Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com> --- v2: Keep btrfs/011 into 'auto' group, to keep the coverage. --- tests/btrfs/group | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)