/usr/lib/blcr-testsuite/run_on is in blcr-testsuite 0.8.2-15ubuntu2.
This file is owned by root:root, with mode 0o755.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 | #!/bin/sh
set -e
. ${cr_testsdir:-`dirname $0`}/shellinit
context=Context1
code=42
trap "\rm -f $context tstmap1 tstmap2 2>/dev/null" 0
#
run_one () {
set +e
${cr_restart} $1 "exit $code" $2
result=$?
if [ $result != $code ]; then
echo "Test of $1 exited with $result when expecting $code"
exit 1
fi
set -e
}
#
# Test group I: Bogus args
#
# Case I.1: bad arguments (args failure)
run_one --run-on-fail-args --bad-argument
# Case I.2: bad file (permanent failure)
run_one --run-on-fail-perm /dev/null
#
# Test group II: Context from save_aux with 1 mmaped file:
#
\rm -f tstmap1
${cr_run} -- ${cr_testsdir}/save_aux "--file $context --clobber" P
# Case II.1: expect success
${cr_restart} $context
# Case II.2: missing file (environmental failure)
\mv -f tstmap1 tstmap2
run_one --run-on-fail-env $context
# Case II.3: expect success to produce special value
\mv -f tstmap2 tstmap1
run_one --run-on-success $context
#
# Test group III: Context from pause
#
\rm -f $context
${cr_run} -- ${cr_testsdir}/pause >/dev/null 2>/dev/null &
pid=$!
sleep 1
${cr_checkpoint} --file $context --clobber --pid $pid
# Case III.1: pid conflict because still running (temporary failure)
run_one --run-on-fail-temp $context
# Cleanup
exec 2>/dev/null # Drop job control message(s)
set +e
kill $pid
wait $pid
exit 0
|