shaba/ostree
1
0
Fork 0
mirror of https://github.com/ostreedev/ostree.git synced 2024-12-23 21:35:26 +03:00
Code Issues Projects Releases Wiki Activity
9695c47684
ostree/Makefile-tests.am

301 lines
10 KiB
Plaintext
Raw Normal View History

Install tests Matching https://live.gnome.org/GnomeGoals/InstalledTests
2013-05-01 23:26:21 +04:00
# Makefile for tests code
#
# Copyright (C) 2013 Colin Walters <walters@verbum.org>
#
# This library is free software; you can redistribute it and/or
# modify it under the terms of the GNU Lesser General Public
# License as published by the Free Software Foundation; either
# version 2 of the License, or (at your option) any later version.
#
# This library is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# Lesser General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public
# License along with this library; if not, write to the
# Free Software Foundation, Inc., 59 Temple Place - Suite 330,
# Boston, MA 02111-1307, USA.
build: distribute TAP helper scripts in tarballs Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #337 Approved by: cgwalters
2016-06-12 12:43:34 +03:00
EXTRA_DIST += \
buildutil/tap-driver.sh \
buildutil/tap-test \
Distribute valgrind suppressions in tarballs Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #557 Approved by: cgwalters
2016-10-08 01:12:29 +03:00
tests/glib.supp \
tests/ostree.supp \
build: distribute TAP helper scripts in tarballs Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #337 Approved by: cgwalters
2016-06-12 12:43:34 +03:00
$(NULL)
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 18:28:04 +03:00
# We should probably consider flipping the default for DEBUG. Also,
# include the builddir in $PATH so we find our just-built ostree
# binary.
TESTS_ENVIRONMENT += OT_TESTS_DEBUG=1 \
Split trivial-httpd into separate binary Working on the libcurl backend, I hit the issue that the trivial-httpd program depends on libsoup. I briefly considered having two versions, but libcurl is client only, and moreover trivial-httpd is no longer trivial - it has various features which are used by the test suite extensively. Hence, what we'll do is build it as a separate binary which links to libsoup, and use it during the tests. We *also* currently still provide `ostree trivial-httpd` since some things use it like `rpm-ostree-toolbox` and the Cockpit tests. After those are ported to use some other webserver, I plan to add a build-time option to drop it. Closes: #636 Approved by: jlebon
2016-12-30 22:18:34 +03:00
OSTREE_UNINSTALLED=$(abs_top_builddir) \
tests: Use G_DEBUG=fatal-warnings here too I am trying to track down a warning I see in `test-keyfile-utils` which turned out to be the installed case only, but let's inject this here too. (The GLib default is broken, but it's hard to fix upstream without breaking the world) Closes: #610 Approved by: jlebon
2016-12-05 20:58:43 +03:00
G_DEBUG=fatal-warnings \
tests: prepend to an existing LD_LIBRARY_PATH, GI_TYPELIB_PATH If we're using LD_LIBRARY_PATH for some locally-built library, we want to search those after OSTree's own libraries. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #606 Approved by: cgwalters
2016-11-30 13:01:05 +03:00
GI_TYPELIB_PATH=$$(cd $(top_builddir) && pwd)$${GI_TYPELIB_PATH:+:$$GI_TYPELIB_PATH} \
LD_LIBRARY_PATH=$$(cd $(top_builddir)/.libs && pwd)$${LD_LIBRARY_PATH:+:$${LD_LIBRARY_PATH}} \
tests: Modernize valgrind infrastructure The recent memleak fixes motivated me to look at the bitrotted code to run invocations of `ostree` in the test suite underneath valgrind. There are a few things here. First, update suppressions file from libhif, since I recently worked on it. When running *uninstalled* as we now support, we need `libtool --mode=execute` in the mix so it expands out to the uninstalled binary and we don't valgrind the intermediate shell. However, it's harder than that because we chdir into a tmpdir, which defeats the libtool logic. AFAICS, the only fix for this is to determine the realbin path before we chdir, and then unfortunately we need to change every use of `ostree` to `${OSTREE}` =( Then this immediately breaks for me on RHEL7 because my ancient copy of `valgrind-3.10.0-16.el7.x86_64` is unaware of syscall 306, i.e. `syncfs`. But let's do this first before I dive into that. Closes: #292 Approved by: krnowak
2016-05-11 22:54:48 +03:00
PATH=$$(cd $(top_builddir)/tests && pwd):$${PATH} \
Load g-i bindings from builddir during build-time testing Previously, the build-time tests would only pass if the g-i bindings to OSTree were already installed, with a reasonably similar version. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #232 Approved by: cgwalters
2016-03-31 11:02:23 +03:00
$(NULL)
Skip gjs-based tests if ASAN is enabled Unfortunately, introspection uses dlopen(), which doesn't quite work when the DSO is compiled with ASAN but the outer executable isn't. Trying to inject LD_PRELOAD=libasan means the outer executable has to be leak free...which, yeah, I'm not going to get into running ASAN today on gjs or pygobject. So, let's skip those tests - ideally, we still run them in some other context without the sanitizers. The coverage we have from them is middling anyways. Closes: #622 Approved by: jlebon
2016-12-08 05:59:40 +03:00
if BUILDOPT_ASAN
TESTS_ENVIRONMENT += OT_SKIP_READDIR_RAND=1 G_SLICE=always-malloc
endif
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 18:28:04 +03:00
Makefile-tests.am: make check uses the built binaries The tests suite was failing locally as it was using the installed version of rofiles-fuse, instead of the built one. Create the needed symlinks in tests/ as we are already doing for the "ostree" binary. ostree-prepare-root and ostree-remount added for completeness. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> Closes: #395 Approved by: cgwalters
2016-07-14 14:42:32 +03:00
uninstalled_test_data = tests/ostree-symlink-stamp tests/ostree-prepare-root-symlink-stamp \
tests/ostree-remount-symlink-stamp tests/rofiles-fuse-symlink-stamp
tests: Modernize valgrind infrastructure The recent memleak fixes motivated me to look at the bitrotted code to run invocations of `ostree` in the test suite underneath valgrind. There are a few things here. First, update suppressions file from libhif, since I recently worked on it. When running *uninstalled* as we now support, we need `libtool --mode=execute` in the mix so it expands out to the uninstalled binary and we don't valgrind the intermediate shell. However, it's harder than that because we chdir into a tmpdir, which defeats the libtool logic. AFAICS, the only fix for this is to determine the realbin path before we chdir, and then unfortunately we need to change every use of `ostree` to `${OSTREE}` =( Then this immediately breaks for me on RHEL7 because my ancient copy of `valgrind-3.10.0-16.el7.x86_64` is unaware of syscall 306, i.e. `syncfs`. But let's do this first before I dive into that. Closes: #292 Approved by: krnowak
2016-05-11 22:54:48 +03:00
build: distribute test scripts in tarballs Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #337 Approved by: cgwalters
2016-06-12 12:39:46 +03:00
dist_uninstalled_test_scripts = tests/test-symbols.sh
tests: Add a test-abi This would have caught a potential ABI regression in https://bugzilla.gnome.org/show_bug.cgi?id=764056 (If we ran this test while building `--without-libarchive`) Pull request: #218 Approved by: jlebon
2016-03-23 22:18:27 +03:00
build: distribute test scripts in tarballs Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #337 Approved by: cgwalters
2016-06-12 12:39:46 +03:00
dist_test_scripts = \
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 18:28:04 +03:00
tests/test-basic.sh \
Fix TAP syntax in test-basic-user.sh, and run it In its initial commit, Alexander Larsson wrote This works standalone, but unfortunately it breaks in gnome-desktop-testing-runner as /tmp doesn't support xattrs, so it is not installed atm. but we now (a) use /var/tmp, and (b) explicitly skip the test if xattr support is unavailable. So it should be OK to run now. Closes: #652 Approved by: cgwalters
2017-01-19 14:21:58 +03:00
tests/test-basic-user.sh \
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 18:28:04 +03:00
tests/test-pull-subpath.sh \
tests/test-archivez.sh \
tests/test-remote-add.sh \
pull: Add support for `http-headers` option Some deployments may want to gate access to content based on things like OAuth. In this model, the client system would normally compute a token and pass it to the server via an API. We could theoretically support this in the remote config too, but that'd be a bit weird for OAuth as the information is dynamic. Therefore this cleans up the code a little bit to more clearly handle the case that the fetcher is initialized from both remote config data plus pull options. Closes: #574 Approved by: giuseppe
2016-11-16 05:03:26 +03:00
tests/test-remote-headers.sh \
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 18:28:04 +03:00
tests/test-remote-gpg-import.sh \
tests/test-commit-sign.sh \
tests/test-export.sh \
tests/test-help.sh \
tests/test-libarchive.sh \
Add test case for inheriting remote options Closes: #236 Approved by: cgwalters
2016-04-01 11:20:34 +03:00
tests/test-parent.sh \
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 18:28:04 +03:00
tests/test-pull-archive-z.sh \
tests/test-pull-commit-only.sh \
tests/test-pull-depth.sh \
tests/test-pull-mirror-summary.sh \
tests/test-pull-large-metadata.sh \
tests/test-pull-metalink.sh \
tests/test-pull-summary-sigs.sh \
tests/test-pull-resume.sh \
tests: Add some test coverage of repeated pulls w/HTTP 500s Systems like pulp may want to keep retrying in a loop if the server throws a (hopefully transient) 500, and we need test coverage of handling these errors versus our existing 404 and 206 coverage. Closes: #383 Approved by: mbarnes
2016-07-08 00:39:07 +03:00
tests/test-pull-repeated.sh \
Add --untrusted option to pull and pull-local https://bugzilla.gnome.org/show_bug.cgi?id=764125 Closes: #221 Approved by: cgwalters
2016-03-23 14:32:03 +03:00
tests/test-pull-untrusted.sh \
tests: Add a big (many objects) pull This would be more likely to tickle things like https://github.com/ostreedev/ostree/issues/601 reliably. Also, while working on the curl backend, I hit on the fact that curl doesn't queue (by default, you can enable) and will happily create 20000+ concurrent TCP connections if you try. Having this test would have made that more likely to fail. Closes: #650 Approved by: giuseppe
2017-01-18 21:35:42 +03:00
tests/test-pull-many.sh \
tests: Add a test for ostree pull --url Closes: #271 Approved by: cgwalters
2016-04-22 15:41:04 +03:00
tests/test-pull-override-url.sh \
Fix local-pull test This was not being run for whatever reason. Also, the test count was wrong. Closes: #237 Approved by: cgwalters
2016-04-04 15:43:33 +03:00
tests/test-local-pull.sh \
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 18:28:04 +03:00
tests/test-local-pull-depth.sh \
tests/test-gpg-signed-commit.sh \
tests/test-admin-upgrade-unconfigured.sh \
tests/test-admin-deploy-syslinux.sh \
tests/test-admin-deploy-2.sh \
tests/test-admin-deploy-karg.sh \
tests/test-admin-deploy-switch.sh \
tests/test-admin-deploy-etcmerge-cornercases.sh \
tests/test-admin-deploy-uboot.sh \
Introducing ostree-grub-generator ostree-grub-generator can be used to customize the generated grub.cfg file. Compile time decision ostree-grub-generator vs grub2-mkconfig can be overwritten with the OSTREE_GRUB2_EXEC envvar - useful for auto tests and OS installers. Why this alternative approach: 1) The current approach is less flexible than using a custom 'ostree-grub-generator' script. Each system can adjust this script for its needs, instead of using the hardcoded values from ostree-bootloader-grub2.c. 2) Too much overhead on embedded to generate grub.cfg via /etc/grub.d/ configuration files. It is still possible to do so, even with this patch applied. No need to install grub2 package on a target device. 3) The grub2-mkconfig code path has other issues: https://bugzilla.gnome.org/show_bug.cgi?id=761180 Task: https://bugzilla.gnome.org/show_bug.cgi?id=762220 Closes: #228 Approved by: cgwalters
2016-04-01 14:51:18 +03:00
tests/test-admin-deploy-grub2.sh \
repo: Clean up staging directory for previous boot IDs We had a policy of cleaning up all files in `$repo/tmp` older than one day, but we should really clean up previous bootid staging directories too, as they can potentially take up a lot of disk space. https://bugzilla.gnome.org/show_bug.cgi?id=760531 Closes: #170 Approved by: jlebon
2016-01-13 19:33:54 +03:00
tests/test-admin-deploy-bootid-gc.sh \
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 18:28:04 +03:00
tests/test-admin-instutil-set-kargs.sh \
tests/test-admin-upgrade-not-backwards.sh \
tests/test-admin-pull-deploy-commit.sh \
upgrade: Add support for --pull-only and --deploy-only This makes it easier to script downloading updates in the background, and only do deployments just before rebooting. Partially addresses https://github.com/ostreedev/ostree/issues/640 Closes: #642 Approved by: jlebon
2017-01-05 19:29:41 +03:00
tests/test-admin-pull-deploy-split.sh \
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 18:28:04 +03:00
tests/test-admin-locking.sh \
tests/test-admin-deploy-clean.sh \
tests/test-repo-checkout-subpath.sh \
tests/test-reset-nonlinear.sh \
tests/test-oldstyle-partial.sh \
tests/test-delta.sh \
tests/test-xattrs.sh \
tests/test-auto-summary.sh \
tests/test-prune.sh \
tests/test-refs.sh \
docs: Add a section on writing buildsystems And add a test that is a demo buildsystem.
2016-03-04 05:17:53 +03:00
tests/test-demo-buildsystem.sh \
tests: Add basic tests for ostree-prepare-root These tests use unshare and mount to prepare a fake initrd/early boot directory structure so we can then test ostree-prepare-root. Things that are tested: * Running in an initrd environment * Running without initrd * /var and /sysroot being mounted correctly * /usr being mounted read-only Things not tested (yet): * Running as init - this could be accomplished by unsharing the pid namespace too. * mounting/unmounting `/proc` if `/proc/cmdline` isn't available * Persistent overlayfs for `/usr` * Probably other things The tests are basic but can be extended in the future as we do more work on `ostree-prepare-root`. These tests must be run as root as they require the ability to `mount` and to `unshare` the mount namespace. Perhaps in the future we can use user namespaces for this test once they are more widely available. Closes: #403 Approved by: cgwalters
2016-07-27 18:40:05 +03:00
tests/test-switchroot.sh \
tests: add tests for contenturl and mirrorlist Closes: #469 Approved by: cgwalters
2016-08-25 22:34:34 +03:00
tests/test-pull-contenturl.sh \
tests/test-pull-mirrorlist.sh \
Install tests Matching https://live.gnome.org/GnomeGoals/InstalledTests
2013-05-01 23:26:21 +04:00
$(NULL)
Import rofiles-fuse While it's not strictly tied to OSTree, let's move https://github.com/cgwalters/rofiles-fuse in here because: - It's *very* useful in concert with OSTree - It's tiny - We can reuse OSTree's test, documentation, etc. infrastructure One thing to consider also is that at some point we could experiment with writing a FUSE filesystem for OSTree. This could internalize a better equivalent of `--link-checkout-speedup`, but on the other hand, the cost of walking filesystem trees for these types of operations is really quite small. But if we did decide to do more FUSE things in OSTree, this is a step towards that too.
2016-02-10 14:42:54 +03:00
if BUILDOPT_FUSE
build: distribute test scripts in tarballs Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #337 Approved by: cgwalters
2016-06-12 12:39:46 +03:00
dist_test_scripts += tests/test-rofiles-fuse.sh
Distribute test scripts even if we wouldn't run them This fixes a "make dist" tarball produced on a minimal system and run on a non-minimal system. Automake knows that files that are only conditionally included in dist_whatever_WHATEVER are to be distributed, but it does not do the same for files that are only conditionally included in EXTRA_DIST, which is how glib-tap.mk's various variables like dist_test_scripts work. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #557 Approved by: cgwalters
2016-10-08 01:09:29 +03:00
else
EXTRA_DIST += tests/test-rofiles-fuse.sh
Import rofiles-fuse While it's not strictly tied to OSTree, let's move https://github.com/cgwalters/rofiles-fuse in here because: - It's *very* useful in concert with OSTree - It's tiny - We can reuse OSTree's test, documentation, etc. infrastructure One thing to consider also is that at some point we could experiment with writing a FUSE filesystem for OSTree. This could internalize a better equivalent of `--link-checkout-speedup`, but on the other hand, the cost of walking filesystem trees for these types of operations is really quite small. But if we did decide to do more FUSE things in OSTree, this is a step towards that too.
2016-02-10 14:42:54 +03:00
endif
build: Make libsoup optional again The "remote cookies" code broke this. While I'm not sure anyone is actually using ostree-without-http, it isn't too hard to keep the build time conditional going. Further, this work is preparatory for libcurl porting. Closes: #621 Approved by: jlebon
2016-12-08 05:16:52 +03:00
if USE_LIBSOUP
dist_test_scripts += tests/test-remote-cookies.sh
endif
Skip gjs-based tests if ASAN is enabled Unfortunately, introspection uses dlopen(), which doesn't quite work when the DSO is compiled with ASAN but the outer executable isn't. Trying to inject LD_PRELOAD=libasan means the outer executable has to be leak free...which, yeah, I'm not going to get into running ASAN today on gjs or pygobject. So, let's skip those tests - ideally, we still run them in some other context without the sanitizers. The coverage we have from them is middling anyways. Closes: #622 Approved by: jlebon
2016-12-08 05:59:40 +03:00
# These call into gjs scripts
js_tests = tests/test-corruption.sh tests/test-pull-corruption.sh
tests: Only install test-corruption if gjs is found It now uses a gjs-based helper.
2014-01-21 23:53:06 +04:00
if BUILDOPT_GJS
Skip gjs-based tests if ASAN is enabled Unfortunately, introspection uses dlopen(), which doesn't quite work when the DSO is compiled with ASAN but the outer executable isn't. Trying to inject LD_PRELOAD=libasan means the outer executable has to be leak free...which, yeah, I'm not going to get into running ASAN today on gjs or pygobject. So, let's skip those tests - ideally, we still run them in some other context without the sanitizers. The coverage we have from them is middling anyways. Closes: #622 Approved by: jlebon
2016-12-08 05:59:40 +03:00
dist_test_scripts += $(js_tests)
Distribute test scripts even if we wouldn't run them This fixes a "make dist" tarball produced on a minimal system and run on a non-minimal system. Automake knows that files that are only conditionally included in dist_whatever_WHATEVER are to be distributed, but it does not do the same for files that are only conditionally included in EXTRA_DIST, which is how glib-tap.mk's various variables like dist_test_scripts work. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #557 Approved by: cgwalters
2016-10-08 01:09:29 +03:00
else
EXTRA_DIST += $(js_tests)
tests: Only install test-corruption if gjs is found It now uses a gjs-based helper.
2014-01-21 23:53:06 +04:00
endif
build: distribute test scripts in tarballs Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #337 Approved by: cgwalters
2016-06-12 12:39:46 +03:00
dist_installed_test_data = tests/archive-test.sh \
Install tests Matching https://live.gnome.org/GnomeGoals/InstalledTests
2013-05-01 23:26:21 +04:00
tests/pull-test.sh \
Unify uboot and syslinux test cases The test-admin-deploy-1 was copied into -uboot at some point. But really they should be testing exactly the same thing, except for the bootloader backend. Unify these tests by extracting a common test core.
2014-01-15 18:48:04 +04:00
tests/admin-test.sh \
Split out basic tests from test-basic.sh This will let us reuse them with other repo types https://bugzilla.gnome.org/show_bug.cgi?id=741125
2014-12-05 16:28:16 +03:00
tests/basic-test.sh \
deltas: Heuristically detect endianness for older deltas If the average object size is greater than 4GiB, let's assume we're dealing with opposite endianness. I'm fairly confident no one is going to be shipping peta- or exa- byte size ostree deltas, period. Past the gigabyte scale you really want bittorrent or something.
2016-02-25 01:04:04 +03:00
tests/pre-endian-deltas-repo-big.tar.xz \
tests/pre-endian-deltas-repo-little.tar.xz \
Install tests Matching https://live.gnome.org/GnomeGoals/InstalledTests
2013-05-01 23:26:21 +04:00
$(NULL)
tests: Tweak installed tests to deal with ASAN We need to disable readdir-rand there too. Closes: #622 Approved by: jlebon
2016-12-08 20:50:20 +03:00
EXTRA_DIST += tests/libtest.sh
Make corrupt-repo-ref.js executable Debian's Lintian packaging consistency check complains that it isn't executable but has a #! line. In fact it's reasonable to run this script directly, so make it executable, and put it in a _scripts variable so it will be installed executable. Closes: #652 Approved by: cgwalters
2017-01-19 14:34:57 +03:00
dist_test_extra_scripts = \
tests/bootloader-entries-crosscheck.py \
tests/corrupt-repo-ref.js \
tests/ostree-grub-generator \
$(NULL)
tests: Add a crosscheck for syslinux bootloader config generation And actually wire this one up in admin-test.sh.
2015-05-28 03:08:44 +03:00
build: Don't install test data without --enable-installed-tests Otherwise $(installed_testdir) is empty so we try to put content in `/`, which I noticed when trying to build an RPM (it works works fine `sudo make install`).
2016-03-08 21:12:00 +03:00
# We can't use nobase_ as we need to strip off the tests/, can't
# use plain installed_ as we do need the gpghome/ prefix.
if ENABLE_INSTALLED_TESTS
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 18:28:04 +03:00
gpginsttestdir = $(installed_testdir)/gpghome
build: distribute more test files Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #337 Approved by: cgwalters
2016-06-12 12:45:48 +03:00
dist_gpginsttest_DATA = tests/gpghome/secring.gpg \
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 18:28:04 +03:00
tests/gpghome/pubring.gpg \
tests: Add test-remote-gpg-import.sh
2015-05-07 20:42:19 +03:00
tests/gpghome/trustdb.gpg \
tests/gpghome/key1.asc \
tests/gpghome/key2.asc \
tests/gpghome/key3.asc
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 18:28:04 +03:00
gpginsttest_trusteddir = $(installed_testdir)/gpghome/trusted
build: distribute more test files Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #337 Approved by: cgwalters
2016-06-12 12:45:48 +03:00
dist_gpginsttest_trusted_DATA = tests/gpghome/trusted/pubring.gpg
tests: Fix up GPG tests for more strict EL7 GPG These GPG tests were failing for me on EL7 - it appears to be because we had only one directory for both private and public keys, and we were giving that to ostree for verification, which passed them onto gpgv. In EL7 beta at least, gpgv now barfs if it finds a private key where it is just expecting to find public keys. Fix this by splitting out the public trusted directory from the private key directory. Except now for signing, we still need the public key there, so symlink it. Whee!
2014-02-10 18:38:07 +04:00
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 18:28:04 +03:00
gpgvinsttestdir = $(installed_testdir)/gpg-verify-data
build: distribute more test files Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #337 Approved by: cgwalters
2016-06-12 12:45:48 +03:00
dist_gpgvinsttest_DATA = $(addprefix tests/gpg-verify-data/, \
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 18:28:04 +03:00
gpg.conf lgpl2 lgpl2.sig pubring.gpg secring.gpg trustdb.gpg)
build: Don't install test data without --enable-installed-tests Otherwise $(installed_testdir) is empty so we try to put content in `/`, which I noticed when trying to build an RPM (it works works fine `sudo make install`).
2016-03-08 21:12:00 +03:00
endif
tests: Restore accidentally deleted Makefile bit Not sure how this got deleted...
2015-02-16 18:29:14 +03:00
Distribute test scripts even if we wouldn't run them This fixes a "make dist" tarball produced on a minimal system and run on a non-minimal system. Automake knows that files that are only conditionally included in dist_whatever_WHATEVER are to be distributed, but it does not do the same for files that are only conditionally included in EXTRA_DIST, which is how glib-tap.mk's various variables like dist_test_scripts work. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #557 Approved by: cgwalters
2016-10-08 01:09:29 +03:00
js_installed_tests = \
tests/test-core.js \
core: Add size information to commit metadata Add a --generate-sizes option to commit to add size information to the commit metadata. This will be used by higher level code which wants to determine the total size necessary for downloading.
2013-10-09 06:44:39 +04:00
tests/test-sizes.js \
Revert "Disable test-sysroot.test" This reverts commit 73868a96d14fa13e69d9df778d2363b89f41fef5.
2014-03-19 17:15:29 +04:00
tests/test-sysroot.js \
tests: Add a simple test-sysroot.js that covers OSTree.Sysroot This will be more interesting as a test case user of the API.
2013-10-03 03:47:38 +04:00
$(NULL)
Distribute test scripts even if we wouldn't run them This fixes a "make dist" tarball produced on a minimal system and run on a non-minimal system. Automake knows that files that are only conditionally included in dist_whatever_WHATEVER are to be distributed, but it does not do the same for files that are only conditionally included in EXTRA_DIST, which is how glib-tap.mk's various variables like dist_test_scripts work. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #557 Approved by: cgwalters
2016-10-08 01:09:29 +03:00
if BUILDOPT_GJS
dist_installed_test_scripts = $(js_installed_tests)
else
EXTRA_DIST += $(js_installed_tests)
tests: Add a gjs-based test This covers introspection, and in general is a much better way to get API coverage tests.
2013-09-18 20:01:46 +04:00
endif
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 18:28:04 +03:00
test_ltlibraries = libreaddir-rand.la
tests: Run all tests through a randomized readdir() Having undefined (but in practice rarely changing) ordering for `readdir()` ended up screwing us over for bootloader config generation; see https://bugzilla.redhat.com/show_bug.cgi?id=1226520 Let's make things significantly more likely to fail more quickly in the future if similar bugs are introduced. We accomplish this by introducing a little `LD_PRELOAD` library that randomizes the results of `readdir()`.
2015-06-02 05:34:14 +03:00
libreaddir_rand_la_SOURCES = tests/readdir-rand.c
build: Fix libreaddir-rand to honor global CFLAGS It's unfortunate that in automake one has to explicitly include the globa `$(AM_CFLAGS)` if one sets `CFLAGS`, and similarly for other variables. I'm trying to use `-fsanitize=address`, and not including it was causing linker failures. We also weren't inheriting the global warnings etc., so I had to fix a decl-after-statement. Closes: #351 Approved by: jlebon
2016-06-17 16:36:51 +03:00
libreaddir_rand_la_CFLAGS = $(AM_CFLAGS) $(OT_INTERNAL_GIO_UNIX_CFLAGS)
Link libreaddir-rand to libdl It uses dlsym(). There's no point in being extra-portable here because OSTree only targets Linux anyway. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #336 Approved by: cgwalters
2016-06-12 17:25:21 +03:00
libreaddir_rand_la_LIBADD = \
-ldl \
$(OT_INTERNAL_GIO_UNIX_LIBS) \
$(NULL)
build: Fix libreaddir-rand to honor global CFLAGS It's unfortunate that in automake one has to explicitly include the globa `$(AM_CFLAGS)` if one sets `CFLAGS`, and similarly for other variables. I'm trying to use `-fsanitize=address`, and not including it was causing linker failures. We also weren't inheriting the global warnings etc., so I had to fix a decl-after-statement. Closes: #351 Approved by: jlebon
2016-06-17 16:36:51 +03:00
libreaddir_rand_la_LDFLAGS = $(AM_LDFLAGS) -avoid-version
Force libreaddir-rand to be a shared library If installed-tests are disabled, it would normally be a static (convenience) library, which isn't something we can LD_PRELOAD. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #232 Approved by: cgwalters
2016-03-31 12:17:02 +03:00
if !ENABLE_INSTALLED_TESTS
libreaddir_rand_la_LDFLAGS += -rpath $(abs_builddir)
endif
tests: Run all tests through a randomized readdir() Having undefined (but in practice rarely changing) ordering for `readdir()` ended up screwing us over for bootloader config generation; see https://bugzilla.redhat.com/show_bug.cgi?id=1226520 Let's make things significantly more likely to fail more quickly in the future if similar bugs are introduced. We accomplish this by introducing a little `LD_PRELOAD` library that randomizes the results of `readdir()`.
2015-06-02 05:34:14 +03:00
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 18:28:04 +03:00
test_programs = tests/test-varint tests/test-ot-unix-utils tests/test-bsdiff tests/test-mutable-tree \
gpg: Add OstreeGpgVerifyResult Wrappers a referenced gpgme_verify_result_t so detailed verify results can be examined independently of executing a verify operation. _ostree_gpg_verifier_check_signature() now returns this object instead of a single valid/invalid boolean, but the idea is for OstreeRepo to also return this object for commit signature verification so it can be utilized at the CLI layer (and possibly by other programs).
2015-03-04 20:44:47 +03:00
tests/test-keyfile-utils tests/test-ot-opt-utils tests/test-ot-tool-util \
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 18:05:08 +03:00
tests/test-gpg-verify-result tests/test-checksum tests/test-lzma tests/test-rollsum \
tests/test-pull-c: New test that runs through the pull API via C We have had in the past issues with running `ostree_repo_pull()` multiple times in the same process, embarassingly enough. Nothing in the current test suite covers this, so let's start. Closes: #322 Approved by: jlebon
2016-06-06 21:49:11 +03:00
tests/test-basic-c tests/test-sysroot-c tests/test-pull-c
tests: add test for test-ot-opt-utils. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-03-06 13:38:13 +03:00
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 18:28:04 +03:00
# An interactive tool
noinst_PROGRAMS += tests/test-rollsum-cli
repo: Add ostree_repo_import_archive_to_mtree This is a more flexible version of the previous ostree_repo_write_archive_to_mtree() which took a file reference. This has an extensible options structure, and in particular now supports `ignore_unsupported_content`. I plan to use this for importing Docker images which contain device nodes. (There's no reason for container images to have those, so we'll just ignore them). Also here, just like the export variant, the caller is responsible for setting up libarchive.
2016-02-19 00:49:30 +03:00
if USE_LIBARCHIVE
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 18:28:04 +03:00
test_programs += tests/test-libarchive-import
repo: Add ostree_repo_import_archive_to_mtree This is a more flexible version of the previous ostree_repo_write_archive_to_mtree() which took a file reference. This has an extensible options structure, and in particular now supports `ignore_unsupported_content`. I plan to use this for importing Docker images which contain device nodes. (There's no reason for container images to have those, so we'll just ignore them). Also here, just like the export variant, the caller is responsible for setting up libarchive.
2016-02-19 00:49:30 +03:00
endif
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 18:05:08 +03:00
common_tests_cflags = $(ostree_bin_shared_cflags) $(OT_INTERNAL_GIO_UNIX_CFLAGS) -I$(srcdir)/libglnx
common_tests_ldadd = $(ostree_bin_shared_ldadd) $(OT_INTERNAL_GIO_UNIX_LIBS)
noinst_LTLIBRARIES += libostreetest.la
libostreetest_la_SOURCES = tests/libostreetest.c
libostreetest_la_CFLAGS = $(common_tests_cflags) -I $(srcdir)/tests
libostreetest_la_LIBADD = $(common_tests_ldadd)
TESTS_CFLAGS = $(common_tests_cflags)
TESTS_LDADD = $(common_tests_ldadd) libostreetest.la
tests: Move test-varint and test-rollsum under "make check" "make check" tests are always enabled and they do not require to be installed. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-02-02 14:56:40 +03:00
tests: rename test-rollsum to test-rollsum-cli Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-08-14 09:43:44 +03:00
tests_test_rollsum_cli_SOURCES = src/libostree/ostree-rollsum.c tests/test-rollsum-cli.c
tests_test_rollsum_cli_CFLAGS = $(TESTS_CFLAGS) $(OT_DEP_ZLIB_CFLAGS)
oxidation: Add implementation of bupsplit in Rust This is an initial drop of "oxidation", or adding implementation of components in Rust. The bupsplit code is a good target - no dependencies, just computation. Translation into Rust had a few twists - - The C code relies a lot on overflowing unsigned ints, and also on the C promotion rules for e.g. `uint8_t -> int32_t` - There were some odd loops that I introduced bugs in while translating...in particular, the function always returns `len`, but I mistakenly translated to `len+1`, resulting in an OOB read on the C side, which was hard to debug. On the plus side, an off-by-one array indexing in the Rust code paniced nicely. In practice, we'll need a lot more build infrastructure to make this work, such as using `cargo vendor` when producing build artifacts for example. Also, Cargo is yet another thing we need to cache. Where do we go with this? Well, I think we should merge this, it's not a lot of code. We can just have it be an alternative CI target. Should we do a lot more right now? Probably not immediately, but I find the medium/long term prospects pretty exciting! Closes: #656 Approved by: jlebon
2017-01-25 05:43:53 +03:00
tests_test_rollsum_cli_LDADD = $(bupsplitpath) $(TESTS_LDADD) $(OT_DEP_ZLIB_LIBS)
tests: Move test-varint and test-rollsum under "make check" "make check" tests are always enabled and they do not require to be installed. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-02-02 14:56:40 +03:00
tests: Add tests for rollsum
2015-08-25 16:27:56 +03:00
tests_test_rollsum_SOURCES = src/libostree/ostree-rollsum.c tests/test-rollsum.c
tests_test_rollsum_CFLAGS = $(TESTS_CFLAGS) $(OT_DEP_ZLIB_CFLAGS)
oxidation: Add implementation of bupsplit in Rust This is an initial drop of "oxidation", or adding implementation of components in Rust. The bupsplit code is a good target - no dependencies, just computation. Translation into Rust had a few twists - - The C code relies a lot on overflowing unsigned ints, and also on the C promotion rules for e.g. `uint8_t -> int32_t` - There were some odd loops that I introduced bugs in while translating...in particular, the function always returns `len`, but I mistakenly translated to `len+1`, resulting in an OOB read on the C side, which was hard to debug. On the plus side, an off-by-one array indexing in the Rust code paniced nicely. In practice, we'll need a lot more build infrastructure to make this work, such as using `cargo vendor` when producing build artifacts for example. Also, Cargo is yet another thing we need to cache. Where do we go with this? Well, I think we should merge this, it's not a lot of code. We can just have it be an alternative CI target. Should we do a lot more right now? Probably not immediately, but I find the medium/long term prospects pretty exciting! Closes: #656 Approved by: jlebon
2017-01-25 05:43:53 +03:00
tests_test_rollsum_LDADD = $(bupsplitpath) $(TESTS_LDADD) $(OT_DEP_ZLIB_LIBS)
tests: Add tests for rollsum
2015-08-25 16:27:56 +03:00
tests: add tests for mutable tree. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-03-04 16:14:18 +03:00
tests_test_mutable_tree_CFLAGS = $(TESTS_CFLAGS)
tests_test_mutable_tree_LDADD = $(TESTS_LDADD)
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 18:05:08 +03:00
tests_test_basic_c_CFLAGS = $(TESTS_CFLAGS)
tests_test_basic_c_LDADD = $(TESTS_LDADD)
lib: Add ostree_sysroot_load_if_changed() API This will allow daemons like rpm-ostree to detect if there are any new deployments efficiently, in combination with using inotify. If there are any changes, rpm-ostree wants publish them on DBus. While we're here, add some changes to start doing unit C testing of the sysroot API.
2016-03-03 21:49:54 +03:00
tests_test_sysroot_c_CFLAGS = $(TESTS_CFLAGS)
tests_test_sysroot_c_LDADD = $(TESTS_LDADD)
tests/test-pull-c: New test that runs through the pull API via C We have had in the past issues with running `ostree_repo_pull()` multiple times in the same process, embarassingly enough. Nothing in the current test suite covers this, so let's start. Closes: #322 Approved by: jlebon
2016-06-06 21:49:11 +03:00
tests_test_pull_c_CFLAGS = $(TESTS_CFLAGS)
tests_test_pull_c_LDADD = $(TESTS_LDADD)
tests: Remove some duplications from Makefile-tests.am Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-03-03 16:21:40 +03:00
tests_test_ot_unix_utils_CFLAGS = $(TESTS_CFLAGS)
tests_test_ot_unix_utils_LDADD = $(TESTS_LDADD)
tests: Move test-varint and test-rollsum under "make check" "make check" tests are always enabled and they do not require to be installed. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-02-02 14:56:40 +03:00
tests: Remove some duplications from Makefile-tests.am Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-03-03 16:21:40 +03:00
tests_test_varint_SOURCES = src/libostree/ostree-varint.c tests/test-varint.c
tests_test_varint_CFLAGS = $(TESTS_CFLAGS)
tests_test_varint_LDADD = $(TESTS_LDADD)
tests: add test for bsdiff Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-02-23 12:05:19 +03:00
tests: Remove some duplications from Makefile-tests.am Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-03-03 16:21:40 +03:00
tests_test_bsdiff_CFLAGS = $(TESTS_CFLAGS)
tests_test_bsdiff_LDADD = libbsdiff.la $(TESTS_LDADD)
keyfile-utils: add tests Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-03-05 17:40:52 +03:00
core: new function _ostree_parse_delta_name Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-04-28 18:45:37 +03:00
tests_test_checksum_SOURCES = src/libostree/ostree-core.c tests/test-checksum.c
tests_test_checksum_CFLAGS = $(TESTS_CFLAGS) $(libglnx_cflags)
tests_test_checksum_LDADD = $(TESTS_LDADD)
repo: Add ostree_repo_import_archive_to_mtree This is a more flexible version of the previous ostree_repo_write_archive_to_mtree() which took a file reference. This has an extensible options structure, and in particular now supports `ignore_unsupported_content`. I plan to use this for importing Docker images which contain device nodes. (There's no reason for container images to have those, so we'll just ignore them). Also here, just like the export variant, the caller is responsible for setting up libarchive.
2016-02-19 00:49:30 +03:00
tests_test_libarchive_import_SOURCES = tests/test-libarchive-import.c
test-libarchive: fix underlinking Signed-off-by: Simon McVittie <smcv@debian.org>
2016-03-11 11:46:27 +03:00
tests_test_libarchive_import_CFLAGS = $(TESTS_CFLAGS) $(libglnx_cflags) $(OT_DEP_LIBARCHIVE_CFLAGS)
tests_test_libarchive_import_LDADD = $(TESTS_LDADD) $(OT_DEP_LIBARCHIVE_LIBS)
repo: Add ostree_repo_import_archive_to_mtree This is a more flexible version of the previous ostree_repo_write_archive_to_mtree() which took a file reference. This has an extensible options structure, and in particular now supports `ignore_unsupported_content`. I plan to use this for importing Docker images which contain device nodes. (There's no reason for container images to have those, so we'll just ignore them). Also here, just like the export variant, the caller is responsible for setting up libarchive.
2016-02-19 00:49:30 +03:00
keyfile-utils: add tests Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-03-05 17:40:52 +03:00
tests_test_keyfile_utils_CFLAGS = $(TESTS_CFLAGS)
tests_test_keyfile_utils_LDADD = $(TESTS_LDADD)
tests: add test for test-ot-opt-utils. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-03-06 13:38:13 +03:00
tests_test_ot_opt_utils_CFLAGS = $(TESTS_CFLAGS)
tests_test_ot_opt_utils_LDADD = $(TESTS_LDADD)
tests: Add tests for test-ot-tool-util Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-03-06 14:54:53 +03:00
tests_test_ot_tool_util_CFLAGS = $(TESTS_CFLAGS)
tests_test_ot_tool_util_LDADD = $(TESTS_LDADD)
gpg: Add OstreeGpgVerifyResult Wrappers a referenced gpgme_verify_result_t so detailed verify results can be examined independently of executing a verify operation. _ostree_gpg_verifier_check_signature() now returns this object instead of a single valid/invalid boolean, but the idea is for OstreeRepo to also return this object for commit signature verification so it can be utilized at the CLI layer (and possibly by other programs).
2015-03-04 20:44:47 +03:00
tests: add tests for LZMA compressor and decompressor Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-08-11 12:26:14 +03:00
tests_test_lzma_SOURCES = src/libostree/ostree-lzma-common.c src/libostree/ostree-lzma-compressor.c \
src/libostree/ostree-lzma-decompressor.c tests/test-lzma.c
tests: Build test-lzma with LZMA flags test-lzma builds a copy of the compressor and decompressor directly, so the compiler needs access to the LZMA headers and the linker needs to link the program with liblzma.
2015-08-26 19:54:31 +03:00
tests_test_lzma_CFLAGS = $(TESTS_CFLAGS) $(OT_DEP_LZMA_CFLAGS)
tests_test_lzma_LDADD = $(TESTS_LDADD) $(OT_DEP_LZMA_LIBS)
tests: add tests for LZMA compressor and decompressor Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
2015-08-11 12:26:14 +03:00
gpg: Add OstreeGpgVerifyResult Wrappers a referenced gpgme_verify_result_t so detailed verify results can be examined independently of executing a verify operation. _ostree_gpg_verifier_check_signature() now returns this object instead of a single valid/invalid boolean, but the idea is for OstreeRepo to also return this object for commit signature verification so it can be utilized at the CLI layer (and possibly by other programs).
2015-03-04 20:44:47 +03:00
tests_test_gpg_verify_result_SOURCES = \
src/libostree/ostree-gpg-verify-result-private.h \
tests/test-gpg-verify-result.c
tests: Link test-gpg-verify-result with gpgme This test uses gpgme directly to verify the signatures, so it needs to find the gpgme headers and link with gpgme to ensure the linker can resolve the symbols.
2015-05-13 01:48:22 +03:00
tests_test_gpg_verify_result_CFLAGS = $(TESTS_CFLAGS) $(OT_INTERNAL_GPGME_CFLAGS)
tests_test_gpg_verify_result_LDADD = $(TESTS_LDADD) $(OT_INTERNAL_GPGME_LIBS)
gpg: Add OstreeGpgVerifyResult Wrappers a referenced gpgme_verify_result_t so detailed verify results can be examined independently of executing a verify operation. _ostree_gpg_verifier_check_signature() now returns this object instead of a single valid/invalid boolean, but the idea is for OstreeRepo to also return this object for commit signature verification so it can be utilized at the CLI layer (and possibly by other programs).
2015-03-04 20:44:47 +03:00
EXTRA_DIST += \
tests: add libostreetest.h to EXTRA_DIST Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> Closes: #242 Approved by: cgwalters
2016-04-07 10:53:54 +03:00
tests/libostreetest.h \
build: distribute more test files Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #337 Approved by: cgwalters
2016-06-12 12:45:48 +03:00
tests/libtest.sh \
gpg: Add OstreeGpgVerifyResult Wrappers a referenced gpgme_verify_result_t so detailed verify results can be examined independently of executing a verify operation. _ostree_gpg_verifier_check_signature() now returns this object instead of a single valid/invalid boolean, but the idea is for OstreeRepo to also return this object for commit signature verification so it can be utilized at the CLI layer (and possibly by other programs).
2015-03-04 20:44:47 +03:00
tests/gpg-verify-data/README.md \
tests: Remove gpg verification files from EXTRA_DIST Follow on from 70a11189. These files are already disted. Closes: #372 Approved by: cgwalters
2016-05-13 16:47:09 +03:00
$(NULL)
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 18:28:04 +03:00
build: Make tests/libreaddir-rand.so rule use AM_V_GEN So non-verbose builds don't have a verbose rule smack in the middle. Closes: #241 Approved by: giuseppe
2016-04-07 04:26:38 +03:00
tests/libreaddir-rand.so: Makefile
$(AM_V_GEN) ln -fns ../.libs/libreaddir-rand.so tests
ALL_LOCAL_RULES += tests/libreaddir-rand.so
Makefile-tests.am: make check uses the built binaries The tests suite was failing locally as it was using the installed version of rofiles-fuse, instead of the built one. Create the needed symlinks in tests/ as we are already doing for the "ostree" binary. ostree-prepare-root and ostree-remount added for completeness. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> Closes: #395 Approved by: cgwalters
2016-07-14 14:42:32 +03:00
CLEANFILES += tests/libreaddir-rand.so tests/ostree-symlink-stamp \
tests/ostree-prepare-root-symlink-stamp tests/ostree-remount-symlink-stamp \
tests/rofiles-fuse-symlink-stamp tests/ostree
build: Update .gitignore The patch to add more symlink bits also needed CLEANFILES updates. Closes: #446 Approved by: jlebon
2016-08-09 03:19:54 +03:00
CLEANFILES += tests/ostree-prepare-root tests/ostree-remount tests/rofiles-fuse
tests: Modernize valgrind infrastructure The recent memleak fixes motivated me to look at the bitrotted code to run invocations of `ostree` in the test suite underneath valgrind. There are a few things here. First, update suppressions file from libhif, since I recently worked on it. When running *uninstalled* as we now support, we need `libtool --mode=execute` in the mix so it expands out to the uninstalled binary and we don't valgrind the intermediate shell. However, it's harder than that because we chdir into a tmpdir, which defeats the libtool logic. AFAICS, the only fix for this is to determine the realbin path before we chdir, and then unfortunately we need to change every use of `ostree` to `${OSTREE}` =( Then this immediately breaks for me on RHEL7 because my ancient copy of `valgrind-3.10.0-16.el7.x86_64` is unaware of syscall 306, i.e. `syncfs`. But let's do this first before I dive into that. Closes: #292 Approved by: krnowak
2016-05-11 22:54:48 +03:00
build: Make symlink depend on source Closes: https://github.com/ostreedev/ostree/issues/389 Closes: #400 Approved by: smcv
2016-07-15 18:17:43 +03:00
tests/%-symlink-stamp: % Makefile
$(AM_V_GEN) set -e; \
Makefile-tests.am: make check uses the built binaries The tests suite was failing locally as it was using the installed version of rofiles-fuse, instead of the built one. Create the needed symlinks in tests/ as we are already doing for the "ostree" binary. ostree-prepare-root and ostree-remount added for completeness. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> Closes: #395 Approved by: cgwalters
2016-07-14 14:42:32 +03:00
lt_bin=`cd $(top_builddir) && ./libtool --mode=execute echo $*`; \
if test "$${lt_bin}" = "$*"; then \
real_bin=$(abs_top_builddir)/$*; \
else \
real_bin="$${lt_bin}"; \
fi; \
ln -sf "$${real_bin}" tests/$*; \
tests: Modernize valgrind infrastructure The recent memleak fixes motivated me to look at the bitrotted code to run invocations of `ostree` in the test suite underneath valgrind. There are a few things here. First, update suppressions file from libhif, since I recently worked on it. When running *uninstalled* as we now support, we need `libtool --mode=execute` in the mix so it expands out to the uninstalled binary and we don't valgrind the intermediate shell. However, it's harder than that because we chdir into a tmpdir, which defeats the libtool logic. AFAICS, the only fix for this is to determine the realbin path before we chdir, and then unfortunately we need to change every use of `ostree` to `${OSTREE}` =( Then this immediately breaks for me on RHEL7 because my ancient copy of `valgrind-3.10.0-16.el7.x86_64` is unaware of syscall 306, i.e. `syncfs`. But let's do this first before I dive into that. Closes: #292 Approved by: krnowak
2016-05-11 22:54:48 +03:00
touch $@
Symlink libreaddir-rand.so into tests directory This means it can be LD_PRELOADed during build-time testing. Signed-off-by: Simon McVittie <smcv@debian.org> Closes: #232 Approved by: cgwalters
2016-03-28 15:46:23 +03:00
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 18:28:04 +03:00
# Unfortunately the glib test data APIs don't actually handle
# non-recursive Automake, so we change our code to canonically look
# for tests/ which is just a symlink when installed.
build: Don't install test data without --enable-installed-tests Otherwise $(installed_testdir) is empty so we try to put content in `/`, which I noticed when trying to build an RPM (it works works fine `sudo make install`).
2016-03-08 21:12:00 +03:00
if ENABLE_INSTALLED_TESTS
ci: Combine UBSAN and ASAN by default I only recently realized this was possible. While we're still seeing leaks in the CI environment for some reason, adding ASAN gives us use-after-free detection etc., which is obviously still very useful even if we're not doing leak checking. Closes: #622 Approved by: jlebon
2016-12-08 05:26:43 +03:00
install-installed-tests-extra:
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 18:28:04 +03:00
if test -L $(DESTDIR)$(installed_testdir)/tests; then \
rm $(DESTDIR)$(installed_testdir)/tests; \
fi
ln -s . $(DESTDIR)$(installed_testdir)/tests
tests: Tweak installed tests to deal with ASAN We need to disable readdir-rand there too. Closes: #622 Approved by: jlebon
2016-12-08 20:50:20 +03:00
if BUILDOPT_ASAN
sed -e 's,^BUILT_WITH_ASAN=.*,BUILT_WITH_ASAN=1,' < $(srcdir)/tests/libtest.sh > $(DESTDIR)$(installed_testdir)/tests/libtest.sh
else
install -m 0644 $(srcdir)/tests/libtest.sh $(DESTDIR)$(installed_testdir)/tests/libtest.sh
endif
ci: Combine UBSAN and ASAN by default I only recently realized this was possible. While we're still seeing leaks in the CI environment for some reason, adding ASAN gives us use-after-free detection etc., which is obviously still very useful even if we're not doing leak checking. Closes: #622 Approved by: jlebon
2016-12-08 05:26:43 +03:00
INSTALL_DATA_HOOKS += install-installed-tests-extra
build: Don't install test data without --enable-installed-tests Otherwise $(installed_testdir) is empty so we try to put content in `/`, which I noticed when trying to build an RPM (it works works fine `sudo make install`).
2016-03-08 21:12:00 +03:00
endif
Reference in New Issue Copy Permalink