From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: Fix 128 if sudo required
Date: Tue, 19 May 2015 16:57:04 +0100 [thread overview]
Message-ID: <20150519155704.GA25841@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1432032373-19418-1-git-send-email-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
On Tue, May 19, 2015 at 10:46:13AM +0000, Fam Zheng wrote:
> If passwordless "sudo" works, use it in the qemu-io cmd.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> tests/qemu-iotests/128 | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Oops, I'm in the group 'disk' on my workstation so I never noticed that
the user running the test may not have permission to access the block
device.
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-05-19 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 10:46 [Qemu-devel] [PATCH] qemu-iotests: Fix 128 if sudo required Fam Zheng
2015-05-19 15:57 ` Stefan Hajnoczi [this message]
2015-05-26 11:59 ` Kevin Wolf
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=20150519155704.GA25841@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.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).