From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:60113)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1S8WF0-00087H-A5
	for qemu-devel@nongnu.org; Fri, 16 Mar 2012 08:26:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1S8WEb-0003Ze-AV
	for qemu-devel@nongnu.org; Fri, 16 Mar 2012 08:26:41 -0400
Received: from mail-pz0-f45.google.com ([209.85.210.45]:45593)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1S8WEb-0003ZW-3i
	for qemu-devel@nongnu.org; Fri, 16 Mar 2012 08:26:17 -0400
Received: by dadp14 with SMTP id p14so6188487dad.4
	for <qemu-devel@nongnu.org>; Fri, 16 Mar 2012 05:26:15 -0700 (PDT)
Message-ID: <4F633163.2070000@codemonkey.ws>
Date: Fri, 16 Mar 2012 07:26:11 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
References: <20120315080621.GB13870@stefanha-thinkpad.localdomain>
	<4F6224FF.8040606@weilnetz.de>
In-Reply-To: <4F6224FF.8040606@weilnetz.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Adding "make check" to the QEMU buildbot
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Weil <sw@weilnetz.de>
Cc: Daniel Gollub <gollub@b1-systems.de>, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>, qemu-devel@nongnu.org

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.
>
>