diff options
| author | Thomas Huth <thuth@redhat.com> | 2019-12-04 16:46:16 +0100 |
|---|---|---|
| committer | Alex Bennée <alex.bennee@linaro.org> | 2019-12-18 20:17:45 +0000 |
| commit | 4f370b109876e0482d46dbe969f093d7ccf6269e (patch) | |
| tree | 8a81e9f402df57c26b9b9e6836aacc033268cd60 /tests | |
| parent | a0d6d7454adb7255a4be33ae0d6a0ca81991273f (diff) | |
| download | qemu-4f370b109876e0482d46dbe969f093d7ccf6269e.zip qemu-4f370b109876e0482d46dbe969f093d7ccf6269e.tar.gz qemu-4f370b109876e0482d46dbe969f093d7ccf6269e.tar.bz2 | |
tests/test-util-filemonitor: Skip test on non-x86 Travis containers
test-util-filemonitor fails in restricted non-x86 Travis containers
since they apparently blacklisted some required system calls there.
Let's simply skip the test if we detect such an environment.
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Cleber Rosa <crosa@redhat.com>
Tested-by: Cleber Rosa <crosa@redhat.com>
Message-Id: <20191204154618.23560-6-thuth@redhat.com>
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/test-util-filemonitor.c | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/tests/test-util-filemonitor.c b/tests/test-util-filemonitor.c index 301cd2d..45009c6 100644 --- a/tests/test-util-filemonitor.c +++ b/tests/test-util-filemonitor.c @@ -406,11 +406,22 @@ test_file_monitor_events(void) char *pathdst = NULL; QFileMonitorTestData data; GHashTable *ids = g_hash_table_new(g_int64_hash, g_int64_equal); + char *travis_arch; qemu_mutex_init(&data.lock); data.records = NULL; /* + * This test does not work on Travis LXD containers since some + * syscalls are blocked in that environment. + */ + travis_arch = getenv("TRAVIS_ARCH"); + if (travis_arch && !g_str_equal(travis_arch, "x86_64")) { + g_test_skip("Test does not work on non-x86 Travis containers."); + return; + } + + /* * The file monitor needs the main loop running in * order to receive events from inotify. We must * thus spawn a background thread to run an event |