Files
flatpak/tests
Simon McVittie ec81d5c61b test-run: avoid testing cases of filesystem binding that won't work
This test effectively assumed that ${test_builddir} is in /home, /opt,
a non-FHS top level directory, or some other directory that isn't
in dont_mount_in_root[] in flatpak-run.c. In a distro build where
${libexecdir} is below /usr, when running the installed-tests
so ${test_builddir} is ${libexecdir}, this assumption doesn't hold.

We can't just copy the file we're dealing with into a subdirectory
of /tmp or /var/tmp either, because those directories aren't
part of --filesystem=host. Meanwhile, we also don't want to pollute
$HOME with test detritus.

For the best possible coverage given all those constraints, we try
three directories: ${test_builddir}; ${TEST_DATA_DIR}, which is
in /var/tmp; and ~/.flatpak-tests, but only if it already exists.

When testing --[no]filesystem=host overrides, we don't even try
${TEST_DATA_DIR}, because we know it's in /var/tmp which can only
be shared explicitly, but we do try the others.

Signed-off-by: Simon McVittie <smcv@debian.org>
2016-06-16 00:10:42 -04:00
..
2015-08-25 13:16:34 +02:00
2016-02-25 15:27:37 +01:00
2016-06-10 12:59:11 +02:00
2016-06-10 12:59:11 +02:00
2016-06-10 12:59:11 +02:00
2016-02-25 19:03:09 +01:00
2016-05-31 15:16:24 +02:00
2016-06-03 16:04:10 +02:00
2016-06-03 14:30:25 +02:00
2016-06-09 12:43:31 +02:00