From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:48297)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1S8EMT-0008El-HG
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 13:21:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1S8EMN-0008OQ-Dh
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 13:21:13 -0400
Received: from v220110690675601.yourvserver.net ([78.47.199.172]:59558)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1S8EMN-0008O8-6h
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 13:21:07 -0400
Message-ID: <4F6224FF.8040606@weilnetz.de>
Date: Thu, 15 Mar 2012 18:21:03 +0100
From: Stefan Weil <sw@weilnetz.de>
MIME-Version: 1.0
References: <20120315080621.GB13870@stefanha-thinkpad.localdomain>
In-Reply-To: <20120315080621.GB13870@stefanha-thinkpad.localdomain>
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 Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Daniel Gollub <gollub@b1-systems.de>, qemu-devel@nongnu.org

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.

Regards,

Stefan W.