From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, "Thomas Huth" <thuth@redhat.com>,
berrange@redhat.com, stefanb@linux.vnet.ibm.com,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
richard.henderson@linaro.org, f4bug@amsat.org,
"Alex Bennée" <alex.bennee@linaro.org>,
cota@braap.org, stefanha@redhat.com, marcandre.lureau@redhat.com,
pbonzini@redhat.com, aurelien@aurel32.net
Subject: [PATCH v1 08/16] tests/test-util-filemonitor: Skip test on non-x86 Travis containers
Date: Mon, 16 Dec 2019 11:07:24 +0000 [thread overview]
Message-ID: <20191216110732.24027-9-alex.bennee@linaro.org> (raw)
In-Reply-To: <20191216110732.24027-1-alex.bennee@linaro.org>
From: Thomas Huth <thuth@redhat.com>
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>
Message-Id: <20191204154618.23560-6-thuth@redhat.com>
---
tests/test-util-filemonitor.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/tests/test-util-filemonitor.c b/tests/test-util-filemonitor.c
index 301cd2db619..45009c69f41 100644
--- a/tests/test-util-filemonitor.c
+++ b/tests/test-util-filemonitor.c
@@ -406,10 +406,21 @@ 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
--
2.20.1
next prev parent reply other threads:[~2019-12-16 11:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 11:07 [PATCH v1 00/16] testing and logging changes for master Alex Bennée
2019-12-16 11:07 ` [PATCH v1 01/16] configure: allow disable of cross compilation containers Alex Bennée
2019-12-16 18:59 ` Philippe Mathieu-Daudé
2019-12-18 18:17 ` Richard Henderson
2019-12-16 11:07 ` [PATCH v1 02/16] tests/vm: Allow to set qemu-img path Alex Bennée
2019-12-16 11:07 ` [PATCH v1 03/16] travis.yml: Run tcg tests with tci Alex Bennée
2019-12-17 15:35 ` Richard Henderson
2019-12-16 11:07 ` [PATCH v1 04/16] iotests: Provide a function for checking the creation of huge files Alex Bennée
2019-12-16 11:07 ` [PATCH v1 05/16] iotests: Skip test 060 if it is not possible to create large files Alex Bennée
2019-12-16 11:07 ` [PATCH v1 06/16] iotests: Skip test 079 " Alex Bennée
2019-12-16 19:00 ` Philippe Mathieu-Daudé
2019-12-16 11:07 ` [PATCH v1 07/16] tests/hd-geo-test: Skip test when images can not be created Alex Bennée
2019-12-16 11:07 ` Alex Bennée [this message]
2019-12-16 11:07 ` [PATCH v1 09/16] travis.yml: Enable builds on arm64, ppc64le and s390x Alex Bennée
2019-12-16 11:07 ` [PATCH v1 10/16] ci: build out-of-tree Alex Bennée
2019-12-16 11:21 ` Li-Wen Hsu
2019-12-16 11:07 ` [PATCH v1 11/16] Fix double free issue in qemu_set_log_filename() Alex Bennée
2019-12-16 11:07 ` [PATCH v1 12/16] Cleaned up flow of code in qemu_set_log(), to simplify and clarify Alex Bennée
2019-12-16 11:07 ` [PATCH v1 13/16] Add a mutex to guarantee single writer to qemu_logfile handle Alex Bennée
2019-12-16 11:07 ` [PATCH v1 14/16] qemu_log_lock/unlock now preserves the " Alex Bennée
2019-12-16 11:07 ` [PATCH v1 15/16] Add use of RCU for qemu_logfile Alex Bennée
2019-12-16 11:07 ` [PATCH v1 16/16] Added tests for close and change of logfile Alex Bennée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191216110732.24027-9-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=cota@braap.org \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).