systemd-stable/test/TEST-32-OOMPOLICY/test.sh

#!/usr/bin/env bash
set -e
TEST_DESCRIPTION="test OOM killer logic"
TEST_NO_NSPAWN=1

. $TEST_BASE_DIR/test-functions

UNIFIED_CGROUP_HIERARCHY=yes

test_setup() {
    create_empty_image_rootdir

    (
        LOG_LEVEL=5
        eval $(udevadm info --export --query=env --name=${LOOPDEV}p2)

        setup_basic_environment
        mask_supporting_services
    )
}

do_test "$@" 32
treewide: more portable bash shebangs As in 2a5fcfae024ffc370bb780572279f45a1da3f946 and in 3e67e5c9928f8b1e1c5a63def88d53ed1fed12eb using /usr/bin/env allows bash to be looked up in PATH rather than being hard-coded. As with the previous changes the same arguments apply - distributions have scripts to rewrite shebangs on installation and they know what locations to rely on. - For tests/compilation we should rather rely on the user to have setup there PATH correctly. In particular this makes testing from git easier on NixOS where do not provide /bin/bash to improve compose-ability. 2020-03-04 12:35:06 +03:00			`#!/usr/bin/env bash`
test: add test case for new OOM logic 2019-03-19 21:54:46 +03:00			`set -e`
			`TEST_DESCRIPTION="test OOM killer logic"`
			`TEST_NO_NSPAWN=1`

			`. $TEST_BASE_DIR/test-functions`

			`UNIFIED_CGROUP_HIERARCHY=yes`

			`test_setup() {`
test: add create_empty_image_rootdir() to simplify testcase setup Almost all tests were manually mounting/unmounting $TESTDIR/root from the loopback image; this moves all that into test-functions so the test setup functions are simplier. Also add test_setup_cleanup() function, to cleanup what is mounted by create_empty_image_rootdir() 2019-07-12 18:47:26 +03:00			`create_empty_image_rootdir`
test: add test case for new OOM logic 2019-03-19 21:54:46 +03:00
			`(`
			`LOG_LEVEL=5`
			`eval $(udevadm info --export --query=env --name=${LOOPDEV}p2)`

			`setup_basic_environment`
test: add function to reduce copied setup boilerplate Many tests were also masking systemd-machined.service. But machined should only start when activated, so having it not masked shouldn't be noticable. TEST-25-IMPORT needs it. 2019-10-08 10:10:12 +03:00			`mask_supporting_services`
test: drop \|\| return 1 expression which is incompatible with set -e The `set -e` option is incompatible with a subshell/compound command, which is followed by \|\| <EXPR>. In such case, the -e option is ignored in all affected subshells/functions (see man bash(1) for command `set`). 2019-07-08 22:11:32 +03:00			`)`
test: add test case for new OOM logic 2019-03-19 21:54:46 +03:00			`}`

test: move TEST-32-OOMPOLICY setup to static files 2019-12-10 11:43:14 +03:00			`do_test "$@" 32`