From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48095)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1bXIdW-00041a-MZ
	for qemu-devel@nongnu.org; Tue, 09 Aug 2016 21:48:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1bXIdQ-0006hH-Ra
	for qemu-devel@nongnu.org; Tue, 09 Aug 2016 21:48:49 -0400
Received: from mx1.redhat.com ([209.132.183.28]:52666)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1bXIdQ-0006h0-M4
	for qemu-devel@nongnu.org; Tue, 09 Aug 2016 21:48:44 -0400
Received: from int-mx13.intmail.prod.int.phx2.redhat.com
	(int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mx1.redhat.com (Postfix) with ESMTPS id AA20B4E324
	for <qemu-devel@nongnu.org>; Wed, 10 Aug 2016 01:48:42 +0000 (UTC)
Date: Wed, 10 Aug 2016 09:41:40 +0800
From: Fam Zheng <famz@redhat.com>
Message-ID: <20160810014140.GD11351@al.usersys.redhat.com>
References: <1470756748-18933-1-git-send-email-berrange@redhat.com>
	<20160809170333.131781.95394@ex-std-node742.prod.rhcloud.com>
	<20160809171151.GO1530@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160809171151.GO1530@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.8 v1 00/60] Modular build of trace
 event files
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: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com

On Tue, 08/09 18:11, Daniel P. Berrange wrote:
> 
> Can we get this report to include details of the
> 
>   a) the software versions of gcc, binutils, and any -devel packages
>      we're building against
> 
>   b) the exact arguments + env variables used to invoke configure,
>      not merely its output
> 
> so we don't have to go digging into the docker test systemm to
> try and reverse engineer this info

The whole point of docker test system is offer a relatively easy reproducer to
developers, so I'm reluctant to engineer patchew or the test script it runs for
that.

On the other hand, it's reasonable to allow the docker testing code to be more
verbose than currently.  Or maybe we can patch ./configure to output these
information?

Fam