ceph/qa/run_xfstests_qemu.sh

#!/usr/bin/env bash
#
# TODO switch to run_xfstests.sh (see run_xfstests_krbd.sh)

set -x

[ -n "${TESTDIR}" ] || export TESTDIR="/tmp/cephtest"
[ -d "${TESTDIR}" ] || mkdir "${TESTDIR}"

URL_BASE="https://git.ceph.com/?p=ceph.git;a=blob_plain;f=qa"
SCRIPT="run_xfstests-obsolete.sh"

cd "${TESTDIR}"

wget -O "${SCRIPT}" "${URL_BASE}/${SCRIPT}"
chmod +x "${SCRIPT}"

# tests excluded fail in the current testing vm regardless of whether
# rbd is used

./"${SCRIPT}" -c 1 -f xfs -t /dev/vdb -s /dev/vdc \
    1-7 9-17 19-26 28-49 51-61 63 66-67 69-79 83 85-105 108-110 112-135 \
    137-170 174-191 193-204 206-217 220-227 230-231 233 235-241 243-249 \
    251-262 264-278 281-286 288-289
STATUS=$?

rm -f "${SCRIPT}"

exit "${STATUS}"
scripts: fix bash path in shebangs /bin/bash is a Linuxism. Other operating systems install bash to different paths. Use /usr/bin/env in shebangs to find bash. Signed-off-by: Alan Somers <asomers@gmail.com> 2017-07-20 22:26:42 +00:00			`#!/usr/bin/env bash`
qa: cp run_xfstests.sh run_xfstests-obsolete.sh run_xfstests.sh is going to be updated in the next commit to be able to drive newer xfstests. Among other things, the new xfstests proper doesn't support listing tests in ranges, which is what the qemu wrapper (run_xfstests_qemu.sh) relies on. So keep a copy of the old run_xfstests.sh around until the qemu vm image is regenerated and the up-to-date exclusion list for that kernel is shaken out. Signed-off-by: Ilya Dryomov <ilya.dryomov@inktank.com> 2014-05-30 09:37:04 +00:00			`#`
			`# TODO switch to run_xfstests.sh (see run_xfstests_krbd.sh)`

			`set -x`

			`[ -n "${TESTDIR}" ] \|\| export TESTDIR="/tmp/cephtest"`
			`[ -d "${TESTDIR}" ] \|\| mkdir "${TESTDIR}"`

qa: https://ceph.com/git -> https://git.ceph.com Signed-off-by: Sage Weil <sage@redhat.com> 2015-09-24 22:36:57 +00:00			`URL_BASE="https://git.ceph.com/?p=ceph.git;a=blob_plain;f=qa"`
qa: cp run_xfstests.sh run_xfstests-obsolete.sh run_xfstests.sh is going to be updated in the next commit to be able to drive newer xfstests. Among other things, the new xfstests proper doesn't support listing tests in ranges, which is what the qemu wrapper (run_xfstests_qemu.sh) relies on. So keep a copy of the old run_xfstests.sh around until the qemu vm image is regenerated and the up-to-date exclusion list for that kernel is shaken out. Signed-off-by: Ilya Dryomov <ilya.dryomov@inktank.com> 2014-05-30 09:37:04 +00:00			`SCRIPT="run_xfstests-obsolete.sh"`

			`cd "${TESTDIR}"`

			`wget -O "${SCRIPT}" "${URL_BASE}/${SCRIPT}"`
			`chmod +x "${SCRIPT}"`
qa: add script for running xfstests in a vm Signed-off-by: Josh Durgin <josh.durgin@inktank.com> 2012-12-05 23:54:11 +00:00
qa: exclude some more xfstests These worked on a newer kernel, but I forgot I had not updated it for the final image. Signed-off-by: Josh Durgin <josh.durgin@inktank.com> 2012-12-12 01:18:14 +00:00			`# tests excluded fail in the current testing vm regardless of whether`
			`# rbd is used`

qa: cp run_xfstests.sh run_xfstests-obsolete.sh run_xfstests.sh is going to be updated in the next commit to be able to drive newer xfstests. Among other things, the new xfstests proper doesn't support listing tests in ranges, which is what the qemu wrapper (run_xfstests_qemu.sh) relies on. So keep a copy of the old run_xfstests.sh around until the qemu vm image is regenerated and the up-to-date exclusion list for that kernel is shaken out. Signed-off-by: Ilya Dryomov <ilya.dryomov@inktank.com> 2014-05-30 09:37:04 +00:00			`./"${SCRIPT}" -c 1 -f xfs -t /dev/vdb -s /dev/vdc \`
			`1-7 9-17 19-26 28-49 51-61 63 66-67 69-79 83 85-105 108-110 112-135 \`
			`137-170 174-191 193-204 206-217 220-227 230-231 233 235-241 243-249 \`
			`251-262 264-278 281-286 288-289`
			`STATUS=$?`

			`rm -f "${SCRIPT}"`

			`exit "${STATUS}"`