From: Stefan Hajnoczi <stefanha@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v4 2/3] coroutine: add check-coroutine automated tests
Date: Mon, 23 May 2011 06:34:46 +0100 [thread overview]
Message-ID: <BANLkTimMJTOsFHAQhpCXu3vrWH_x0bNpFQ@mail.gmail.com> (raw)
In-Reply-To: <4DD6E7D0.7060409@codemonkey.ws>
On Fri, May 20, 2011 at 11:14 PM, Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 05/20/2011 05:59 AM, Stefan Hajnoczi wrote:
>>
>> To run automated tests for coroutines:
>>
>> make check-coroutine
>> ./check-coroutine
>>
>> On success the program terminates with exit status 0. On failure an
>> error message is written to stderr and the program exits with exit
>> status 1.
>>
>> Signed-off-by: Stefan Hajnoczi<stefanha@linux.vnet.ibm.com>
>
> Can you include the glib patch and switch this to a gtest based test? I
> don't want to introduce more libcheck tests.
This isn't a libcheck test. I'm happy to user gtester though.
Stefan
next prev parent reply other threads:[~2011-05-23 5:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 10:59 [Qemu-devel] [PATCH v4 0/3] Coroutines for better asynchronous programming Stefan Hajnoczi
2011-05-20 10:59 ` [Qemu-devel] [PATCH v4 1/3] coroutine: introduce coroutines Stefan Hajnoczi
2011-05-20 12:09 ` Paolo Bonzini
2011-05-20 12:32 ` Stefan Hajnoczi
2011-05-21 7:35 ` Blue Swirl
2011-05-20 10:59 ` [Qemu-devel] [PATCH v4 2/3] coroutine: add check-coroutine automated tests Stefan Hajnoczi
2011-05-20 22:14 ` Anthony Liguori
2011-05-23 5:34 ` Stefan Hajnoczi [this message]
2011-05-20 10:59 ` [Qemu-devel] [PATCH v4 3/3] coroutine: add check-coroutine --benchmark-lifecycle Stefan Hajnoczi
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=BANLkTimMJTOsFHAQhpCXu3vrWH_x0bNpFQ@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).