check: back off the OOM score adjustment to -500

Dave Chinner complained that fstests really shouldn't be running at
-1000 oom score adjustment because that makes it more "important" than
certain system daemons (e.g. journald, udev).  That's true, so increase
it to -500.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>

diff --git a/check b/check
index 242cb8c1e6f71004e5fb531e7b79e1cada2e8431..a08631213cbb004db5b0febed885ad06331b0a12 100755 (executable)
--- a/check
+++ b/check
@@ -564,7 +564,7 @@ OOM_SCORE_ADJ="/proc/self/oom_score_adj"
 function _adjust_oom_score() {
        test -w "${OOM_SCORE_ADJ}" && echo "$1" > "${OOM_SCORE_ADJ}"
 }
 function _adjust_oom_score() {
        test -w "${OOM_SCORE_ADJ}" && echo "$1" > "${OOM_SCORE_ADJ}"
 }

-_adjust_oom_score -1000
+_adjust_oom_score -500

 
 # ...and make the tests themselves somewhat more attractive to it, so that if
 # the system runs out of memory it'll be the test that gets killed and not the
 
 # ...and make the tests themselves somewhat more attractive to it, so that if
 # the system runs out of memory it'll be the test that gets killed and not the