From: Sascha Silbe <silbe@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PATCH for-v2.7 v2 0/2] test-logging: don't hard-code paths in /tmp
Date: Thu, 18 Aug 2016 20:46:01 +0200 [thread overview]
Message-ID: <1471545963-11720-1-git-send-email-silbe@linux.vnet.ibm.com> (raw)
This version should be good enough for inclusion in 2.7. I kept the
temporary directory removal function local to test-logging for now,
only cleaning up a single directory level. We can still factor it out
and make it more generic in the 2.8 cycle. For 2.7 I'd rather stick
with a minimal approach as it's very late in the cycle.
Tested successfully with the centos6 docker image. Apart from a hang
(tests/test-qga) and a race condition (tests/acpi-test-disk.raw
missing) that both happen even without my patches, it also works well
on Ubuntu 14.04.
Feel free to perform any additional fixup required to land this in
rc4; I might not be around again until Tuesday.
Sascha Silbe (2):
glib: add compatibility implementation for g_dir_make_tmp()
test-logging: don't hard-code paths in /tmp
include/glib-compat.h | 21 +++++++++++++++++++++
tests/test-logging.c | 48 +++++++++++++++++++++++++++++++++++++++++-------
2 files changed, 62 insertions(+), 7 deletions(-)
--
1.9.1
next reply other threads:[~2016-08-18 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 18:46 Sascha Silbe [this message]
2016-08-18 18:46 ` [Qemu-devel] [PATCH v2 1/2] glib: add compatibility implementation for g_dir_make_tmp() Sascha Silbe
2016-08-19 11:45 ` Peter Maydell
2016-08-23 13:21 ` Sascha Silbe
2016-08-18 18:46 ` [Qemu-devel] [PATCH v2 2/2] test-logging: don't hard-code paths in /tmp Sascha Silbe
2016-08-19 12:42 ` [Qemu-devel] [PATCH for-v2.7 v2 0/2] " Peter Maydell
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=1471545963-11720-1-git-send-email-silbe@linux.vnet.ibm.com \
--to=silbe@linux.vnet.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).