Whamcloud - gitweb
LU-14104 tests: sanity/123* shouldn't fail performance checks
authorAlex Zhuravlev <bzzz@whamcloud.com>
Mon, 2 Nov 2020 07:13:44 +0000 (10:13 +0300)
committerAndreas Dilger <adilger@whamcloud.com>
Thu, 14 Dec 2023 13:56:17 +0000 (13:56 +0000)
running in VMs as CPU resource isn't strictly guaranteed usually.

Lustre-change: https://review.whamcloud.com/40512
Lustre-commit: b1915f13e3b69c72e3e4c1f2a32d022b6a20d347

Test-Parameters: trivial
Signed-off-by: Alex Zhuravlev <bzzz@whamcloud.com>
Change-Id: Ieec4a89b921f7ccc198eb10513d4980ad3a20b51
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Reviewed-on: https://review.whamcloud.com/c/ex/lustre-release/+/53456
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
lustre/tests/sanity.sh

index b066f1a..d7526df 100755 (executable)
@@ -13202,6 +13202,7 @@ test_123a_base() { # was test 123, statahead(bug 11401)
                log "testing UP system. Performance may be lower than expected."
                SLOWOK=1
        fi
+       running_in_vm && SLOWOK=1
 
        rm -rf $DIR/$tdir
        test_mkdir $DIR/$tdir