criu/test/jenkins/criu-iter.sh

#!/bin/bash

# Make 3 iteration of dump/restore for each test
set -e
source `dirname $0`/criu-lib.sh
prep
mount_tmpfs_to_dump
./test/zdtm.py run --all --keep-going --report report --parallel 4 --iter 3 -x 'maps04' || fail
test/jenkins: use bash to run shell scripts We permanently have issues like this: ./test/jenkins/criu-iter.sh: 3: source: not found It looks like a good idea to use one shell to run our jenkins scripts. Signed-off-by: Andrei Vagin <avagin@gmail.com> 2020-04-18 22:28:24 +03:00			`#!/bin/bash`

test: add scripts, which are used by jenkins (v2) v2: split one job on a few parts Signed-off-by: Andrey Vagin <avagin@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2014-02-25 16:09:00 +04:00			`# Make 3 iteration of dump/restore for each test`
jenkins: use zdtm.py for criu-iter Signed-off-by: Andrew Vagin <avagin@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2015-10-27 18:02:00 +03:00			`set -e`
			source `dirname $0`/criu-lib.sh
			`prep`
jenkins: collect an report for each run Now zdtm.py can construct an report which contains all required inforamtion for investigating a problem. This patch adds support of this functionality to jenkins scripts. Signed-off-by: Andrew Vagin <avagin@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@parallels.com> 2015-10-29 21:45:00 +03:00			`mount_tmpfs_to_dump`
jenkins: change jenkins script to run full set of tests add options --keep-going and --report (if it was absent) to run full testrun with report creation Signed-off-by: Sergey Bronnikov <sergeyb@openvz.org> Acked-by: Andrew Vagin <avagin@virtuozzo.com> Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com> 2016-03-16 18:28:00 +03:00			`./test/zdtm.py run --all --keep-going --report report --parallel 4 --iter 3 -x 'maps04' \|\| fail`