ostree/buildutil/tap-test

#! /bin/bash
#
# Run a test in tap mode, ensuring we have a temporary directory.  We
# always use /var/tmp becuase we might want to use user xattrs, which
# aren't available on tmpfs.
#
# The test binary is passed as $1

srcd=$(cd $(dirname $1) && pwd)
bn=$(basename $1)
tempdir=$(mktemp -d /var/tmp/tap-test.XXXXXX)
touch ${tempdir}/.testtmp
function cleanup () {
    if test -n "${TEST_SKIP_CLEANUP:-}"; then
	echo "Skipping cleanup of ${tempdir}"
    else if test -f ${tempdir}/.testtmp; then
	rm "${tempdir}" -rf
    fi
    fi
}
trap cleanup EXIT
cd ${tempdir}
${srcd}/${bn} -k --tap
tests: Port to glib-tap.mk, make `make check` run all of the tests OSTree's code for testing predates the `glib-tap.mk` making its way into GLib. Let's switch to it, as it provides a number of advantages. By far the biggest advantage is that `make check` can start to run most of the tests in addition to having them work installed. This commit keeps the installed tests working, but `make check` turns out to be really broken because...our TAP usage has bitrotted to say the least. Fix that all up. Do some hacks so that the tests work uninstalled as well - in particular, `glib-tap.mk` and the bits encoded into `g_test_build_filename()` assume recursive Automake (blah). Work around that by creating a symlink when installed to loop back. 2016-03-02 10:28:04 -05:00			`#! /bin/bash`
tests: Unify some tmpdir code, add ability for C to use libtest.sh I want to be able to easily test the C API on actual data in an OSTree repo. The shell `libtest.sh` has code to generate it. Bridge the two worlds by introducing a little `libostreetest` library which has a C API which spawns a shell that runs things in `libtest.sh`. Yes, this is about as beautiful as it sounds, which is to say, it's not. But it works! Note while we were here, I realized we were actually now creating two tmpdirs per test in `make check` because the tap driver was already doing that. Unify it so we know the C code can rely on it. 2016-03-02 10:05:08 -05:00			`#`
			`# Run a test in tap mode, ensuring we have a temporary directory. We`
			`# always use /var/tmp becuase we might want to use user xattrs, which`
			`# aren't available on tmpfs.`
			`#`
			`# The test binary is passed as $1`
tests: Port to glib-tap.mk, make `make check` run all of the tests OSTree's code for testing predates the `glib-tap.mk` making its way into GLib. Let's switch to it, as it provides a number of advantages. By far the biggest advantage is that `make check` can start to run most of the tests in addition to having them work installed. This commit keeps the installed tests working, but `make check` turns out to be really broken because...our TAP usage has bitrotted to say the least. Fix that all up. Do some hacks so that the tests work uninstalled as well - in particular, `glib-tap.mk` and the bits encoded into `g_test_build_filename()` assume recursive Automake (blah). Work around that by creating a symlink when installed to loop back. 2016-03-02 10:28:04 -05:00
			`srcd=$(cd $(dirname $1) && pwd)`
			`bn=$(basename $1)`
tests: Unify some tmpdir code, add ability for C to use libtest.sh I want to be able to easily test the C API on actual data in an OSTree repo. The shell `libtest.sh` has code to generate it. Bridge the two worlds by introducing a little `libostreetest` library which has a C API which spawns a shell that runs things in `libtest.sh`. Yes, this is about as beautiful as it sounds, which is to say, it's not. But it works! Note while we were here, I realized we were actually now creating two tmpdirs per test in `make check` because the tap driver was already doing that. Unify it so we know the C code can rely on it. 2016-03-02 10:05:08 -05:00			`tempdir=$(mktemp -d /var/tmp/tap-test.XXXXXX)`
			`touch ${tempdir}/.testtmp`
tests: Port to glib-tap.mk, make `make check` run all of the tests OSTree's code for testing predates the `glib-tap.mk` making its way into GLib. Let's switch to it, as it provides a number of advantages. By far the biggest advantage is that `make check` can start to run most of the tests in addition to having them work installed. This commit keeps the installed tests working, but `make check` turns out to be really broken because...our TAP usage has bitrotted to say the least. Fix that all up. Do some hacks so that the tests work uninstalled as well - in particular, `glib-tap.mk` and the bits encoded into `g_test_build_filename()` assume recursive Automake (blah). Work around that by creating a symlink when installed to loop back. 2016-03-02 10:28:04 -05:00			`function cleanup () {`
tests: Unify some tmpdir code, add ability for C to use libtest.sh I want to be able to easily test the C API on actual data in an OSTree repo. The shell `libtest.sh` has code to generate it. Bridge the two worlds by introducing a little `libostreetest` library which has a C API which spawns a shell that runs things in `libtest.sh`. Yes, this is about as beautiful as it sounds, which is to say, it's not. But it works! Note while we were here, I realized we were actually now creating two tmpdirs per test in `make check` because the tap driver was already doing that. Unify it so we know the C code can rely on it. 2016-03-02 10:05:08 -05:00			`if test -n "${TEST_SKIP_CLEANUP:-}"; then`
admin: Add an `unlock` command, and libostree API I'm trying to improve the developer experience on OSTree-managed systems, and I had an epiphany the other day - there's no reason we have to be absolutely against mutating the current rootfs live. The key should be making it easy to rollback/reset to a known good state. I see this command as useful for two related but distinct workflows: - `ostree admin unlock` will assume you're doing "development". The semantics hare are that we mount an overlayfs on `/usr`, but the overlay data is in `/var/tmp`, and is thus discarded on reboot. - `ostree admin unlock --hotfix` first clones your current deployment, then creates an overlayfs over `/usr` persistent to this deployment. Persistent in that now the initramfs switchroot tool knows how to mount it as well. In this model, if you want to discard the hotfix, at the moment you roll back/reboot into the clone. Note originally, I tried using `rofiles-fuse` over `/usr` for this, but then everything immediately explodes because the default (at least CentOS 7) SELinux policy denies tons of things (including `sshd_t` access to `fusefs_t`). Sigh. So the switch to `overlayfs` came after experimentation. It still seems to have some issues...specifically `unix_chkpwd` is broken, possibly because it's setuid? Basically I can't ssh in anymore. But I can `rpm -Uvh strace.rpm` which is handy. NOTE: I haven't tested the hotfix path fully yet, specifically the initramfs bits. 2016-03-18 15:32:58 -04:00			`echo "Skipping cleanup of ${tempdir}"`
tap-test: clean up temporary test directories as intended The script created ./.testtmp but looked for ./.test, which isn't going to work. This means the various "ostree trivial-httpd --autoexit" processes actually exit, because their web roots are cleaned up now. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #232 Approved by: cgwalters 2016-03-31 08:24:56 +01:00			`else if test -f ${tempdir}/.testtmp; then`
tests: Unify some tmpdir code, add ability for C to use libtest.sh I want to be able to easily test the C API on actual data in an OSTree repo. The shell `libtest.sh` has code to generate it. Bridge the two worlds by introducing a little `libostreetest` library which has a C API which spawns a shell that runs things in `libtest.sh`. Yes, this is about as beautiful as it sounds, which is to say, it's not. But it works! Note while we were here, I realized we were actually now creating two tmpdirs per test in `make check` because the tap driver was already doing that. Unify it so we know the C code can rely on it. 2016-03-02 10:05:08 -05:00			`rm "${tempdir}" -rf`
			`fi`
			`fi`
tests: Port to glib-tap.mk, make `make check` run all of the tests OSTree's code for testing predates the `glib-tap.mk` making its way into GLib. Let's switch to it, as it provides a number of advantages. By far the biggest advantage is that `make check` can start to run most of the tests in addition to having them work installed. This commit keeps the installed tests working, but `make check` turns out to be really broken because...our TAP usage has bitrotted to say the least. Fix that all up. Do some hacks so that the tests work uninstalled as well - in particular, `glib-tap.mk` and the bits encoded into `g_test_build_filename()` assume recursive Automake (blah). Work around that by creating a symlink when installed to loop back. 2016-03-02 10:28:04 -05:00			`}`
			`trap cleanup EXIT`
			`cd ${tempdir}`
			`${srcd}/${bn} -k --tap`