From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35387) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bXOkM-0003qv-N0 for qemu-devel@nongnu.org; Wed, 10 Aug 2016 04:20:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bXOkH-00057O-NX for qemu-devel@nongnu.org; Wed, 10 Aug 2016 04:20:17 -0400 Received: from mx1.redhat.com ([209.132.183.28]:54286) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bXOkH-00057E-Hc for qemu-devel@nongnu.org; Wed, 10 Aug 2016 04:20:13 -0400 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) (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 D284FC0586CA for ; Wed, 10 Aug 2016 08:20:12 +0000 (UTC) Date: Wed, 10 Aug 2016 16:13:10 +0800 From: Fam Zheng Message-ID: <20160810081310.GB19064@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> <20160810014140.GD11351@al.usersys.redhat.com> <20160810080634.GC13393@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160810080634.GC13393@redhat.com> Subject: Re: [Qemu-devel] [PATCH for-2.8 v1 00/60] Modular build of trace event files List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: qemu-devel@nongnu.org, stefanha@redhat.com On Wed, 08/10 09:06, Daniel P. Berrange wrote: > On Wed, Aug 10, 2016 at 09:41:40AM +0800, Fam Zheng wrote: > > 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. > > That's just pointlessly creating extra work for the developers reading > these build reports. If you outputted the info I suggest, it can help > developers diagnose the problems more quickly. Even if running the > docker env locally is possible & even easy, it doesn't make it faster > than reading the relevant info from email report in front of you. I agree with your point, I just don't know how to do a) neatly, except for a vast change to configure. Fam