From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, thuth@redhat.com, berrange@redhat.com,
f4bug@amsat.org, mreitz@redhat.com, stefanha@redhat.com,
pbonzini@redhat.com, alex.bennee@linaro.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] docs: Add docs/devel/testing.rst
Date: Wed, 31 Jan 2018 08:24:24 -0600 [thread overview]
Message-ID: <5c8b634a-0edd-52af-3f9f-aef0205526c8@redhat.com> (raw)
In-Reply-To: <20180131032800.25578-1-famz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2058 bytes --]
On 01/30/2018 09:28 PM, Fam Zheng wrote:
> To make our efforts on QEMU testing easier to consume by contributors,
> let's add a document. For example, Patchew reports build errors on
> patches that should be relatively easy to reproduce with a few steps, and
> it is much nicer if there is such a documentation that it can refer to.
>
> This focuses on how to run existing tests and how to write new test
> cases, without going into the frameworks themselves.
>
> The VM based testing section is moved from tests/vm/README which now
> is a single line pointing to the new doc.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
>
> +Testing with "make check"
> +=========================
> +
> +The "make check" testing family includes most of the C based tests in QEMU. For
> +a quick help, run ``make check-help`` from the source tree.
> +
> +The usual way to run these tests is:
> +
> +.. code::
> +
> + make check
> +
> +which includes QAPI schema tests, unit tests, and QTests. Different sub-types
> +of "make check" testings will be explained below.
s/testings/tests/ or even s/testings//
> +Since unit tests don't require environment variables, the simplest way to debug
> +a unit test failure is often directly invoking it or even running it under
> +``gdb``. However there can still be differences in behavior between ``make``
> +invocations and your manual run, due to ``$MALLOC_PERTURB_`` environment
> +variable (which affects memory reclaimation and catches invalid pointers
s/reclaimation/reclamation/
> + $ sudo groupadd docker
> + $ sudo usermod $USER -G docker
> + $ sudo chown :docker /var/run/docker.sock
> +
> +Note that any one of above configurations makes it possible for the user to
> +exploit the whole host with Docker bind mounting or other privileged
> +operations. So only do it on developement machines.
s/developement/development/
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2018-01-31 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 3:28 [Qemu-devel] [PATCH v2] docs: Add docs/devel/testing.rst Fam Zheng
2018-01-31 13:45 ` Stefan Hajnoczi
2018-01-31 13:49 ` Andrew Jones
2018-02-01 0:26 ` Fam Zheng
2018-01-31 14:24 ` Eric Blake [this message]
2018-02-01 2:16 ` Fam Zheng
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=5c8b634a-0edd-52af-3f9f-aef0205526c8@redhat.com \
--to=eblake@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).