From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefan Weil <sw@weilnetz.de>
Cc: Daniel Gollub <gollub@b1-systems.de>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Adding "make check" to the QEMU buildbot
Date: Fri, 16 Mar 2012 07:26:11 -0500 [thread overview]
Message-ID: <4F633163.2070000@codemonkey.ws> (raw)
In-Reply-To: <4F6224FF.8040606@weilnetz.de>
On 03/15/2012 12:21 PM, Stefan Weil wrote:
> Am 15.03.2012 09:06, schrieb Stefan Hajnoczi:
>> QEMU has grown a number of sanity tests that can be run using "make
>> check". They are fast and do not require many resources.
>>
>> Is it possible to add "make check" after the build?
>>
>> We may have to deal with some failures in the beginning - either due to
>> buildslave environment or legitimate broken platforms. But I think we
>> can get all green pretty easily.
>>
>> Stefan
>
> You can combine build and check by running "make all check".
> I don't expect much red (if any at all).
>
> The iotests need some disk space (400 MB are sufficient, but I
> don't know the lower limit). An incremental build and check
> takes typically less than 3 minutes on my virtual server.
> I nearly always compile without optimization because that
> speeds compilation a lot, and errors caused by optimization
> are very rare.
>
> Non-Linux hosts currently won't run the iotests.
>
> Cross builds cannot run the tests.
Once qtest gets merged, there will be a make check-report.html which has a nice
HTML output.
Regards,
Anthony Liguori
>
> Regards,
>
> Stefan W.
>
>
prev parent reply other threads:[~2012-03-16 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 8:06 [Qemu-devel] Adding "make check" to the QEMU buildbot Stefan Hajnoczi
2012-03-15 17:21 ` Stefan Weil
2012-03-16 9:30 ` Gerd Hoffmann
2012-03-16 12:26 ` Anthony Liguori [this message]
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=4F633163.2070000@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=gollub@b1-systems.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=sw@weilnetz.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.