From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 02/10] qtest/ahci: add qcow2 support to ahci-test
Date: Thu, 12 Nov 2015 12:05:00 -0500 [thread overview]
Message-ID: <5644C6BC.9030109@redhat.com> (raw)
In-Reply-To: <CAFEAcA-5RMnVCaGMJFvMZ5qqR694tTs4=9UE8ja1MgtvNuvPoQ@mail.gmail.com>
On 11/12/2015 05:59 AM, Peter Maydell wrote:
> On 29 April 2015 at 00:25, John Snow <jsnow@redhat.com> wrote:
>> This will enable the testing of high offsets without
>> wasting a lot of disk space, and does not impact the
>> previous tests.
>>
>> mkimg and mkqcow2 are added to libqos for other tests.
>
>
>> + qemu_img_path = getenv("QTEST_QEMU_IMG");
>> + abs_path = realpath(qemu_img_path, NULL);
>> + assert(qemu_img_path);
>> +
>> + cli = g_strdup_printf("%s create -f %s %s %uM", abs_path,
>> + fmt, file, size_mb);
>> + ret = g_spawn_command_line_sync(cli, &out, &out2, &rc, &err);
>> + if (err) {
>> + fprintf(stderr, "%s\n", err->message);
>> + g_error_free(err);
>> + }
>> + g_assert(ret && !err);
>
> I've just discovered that this change means that "make check"
> will fail on a system which doesn't have an installed qemu-img
> and where the build was configured with --disable-tools, and
> with a confusing error message:
>
> Failed to execute child process "(null)" (No such file or directory)
> **
> ERROR:/Users/pm215/src/qemu/tests/libqos/libqos.c:171:void mkimg(const
> char *, const char *, unsigned int): assertion failed: (ret && !err)
>
> The test should probably be skipped if qemu-img isn't available.
>
> thanks
> -- PMM
>
In part I feel that it's reasonable to expect that you have tools
available in order to run tests, but I don't want to be the first to
break rank.
(At the very least, the error is extremely confusing.)
I'm writing a patch now to skip the LBA48 high-sector tests if qemu-img
isn't available and fall back to raw.
--js
next prev parent reply other threads:[~2015-11-12 17:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 23:25 [Qemu-devel] [PULL 00/10] Ide patches John Snow
2015-04-28 23:25 ` [Qemu-devel] [PULL 01/10] fdc: remove sparc sun4m mutations John Snow
2015-04-28 23:25 ` [Qemu-devel] [PULL 02/10] qtest/ahci: add qcow2 support to ahci-test John Snow
2015-11-12 10:59 ` Peter Maydell
2015-11-12 17:05 ` John Snow [this message]
2015-04-28 23:25 ` [Qemu-devel] [PULL 03/10] qtest/ahci: test different disk sectors John Snow
2015-04-28 23:25 ` [Qemu-devel] [PULL 04/10] qtest/ahci: Add simple flush test John Snow
2015-04-28 23:25 ` [Qemu-devel] [PULL 05/10] qtest/ahci: Allow override of default CLI options John Snow
2015-04-28 23:25 ` [Qemu-devel] [PULL 06/10] libqtest: add qmp_eventwait John Snow
2015-04-28 23:25 ` [Qemu-devel] [PULL 07/10] libqtest: add qmp_async John Snow
2015-04-28 23:25 ` [Qemu-devel] [PULL 08/10] libqos: add blkdebug_prepare_script John Snow
2015-04-28 23:25 ` [Qemu-devel] [PULL 09/10] qtest/ahci: add flush retry test John Snow
2015-04-28 23:25 ` [Qemu-devel] [PULL 10/10] qtest: Add assertion that required environment variable is set John Snow
2015-04-30 10:05 ` [Qemu-devel] [PULL 00/10] Ide patches 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=5644C6BC.9030109@redhat.com \
--to=jsnow@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).