From 18637db7ca6fa92ec6ea494a353a5ec46700a30e Mon Sep 17 00:00:00 2001 From: Yang Sheng Date: Fri, 4 May 2018 18:20:49 +0800 Subject: [PATCH] LU-9966 tests: sanity-411 check LBUG direct The sanity test_411 intends to catch LBUG while IO under memory pressure. It assumes that 'dd' would fail because memory alloction failure. But it is not ture since RHEL7 has some problem in memory accounting. So we can ignore the 'dd' status. Test-Parameters: trivial Signed-off-by: Yang Sheng Change-Id: Ie9af0fe68c85a9e2af4da6b49d0a697d00f3761b Reviewed-on: https://review.whamcloud.com/32293 Tested-by: Jenkins Reviewed-by: John L. Hammond Reviewed-by: Jian Yu Reviewed-by: Andreas Dilger Tested-by: Andreas Dilger --- lustre/tests/sanity.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lustre/tests/sanity.sh b/lustre/tests/sanity.sh index 0166c90..505e190 100755 --- a/lustre/tests/sanity.sh +++ b/lustre/tests/sanity.sh @@ -19038,9 +19038,9 @@ test_411() { echo 1M > $cgdir/memory.limit_in_bytes # Should not LBUG, just be killed by oom-killer - sh -c "echo \$$ > $cgdir/tasks && dd if=$DIR/$tfile of=/dev/null" && - error "fail to trigger a memory allocation error" - + # dd will return 0 even allocation failure in some environment. + # So don't check return value + sh -c "echo \$$ > $cgdir/tasks && dd if=$DIR/$tfile of=/dev/null" cleanup_test411_cgroup $cgdir return 0 -- 1.8.3.1