From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46615)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1b8dAX-0006im-39
	for qemu-devel@nongnu.org; Thu, 02 Jun 2016 20:40:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1b8dAT-0007WW-UU
	for qemu-devel@nongnu.org; Thu, 02 Jun 2016 20:40:57 -0400
Received: from mx1.redhat.com ([209.132.183.28]:59385)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <famz@redhat.com>) id 1b8dAT-0007WI-P9
	for qemu-devel@nongnu.org; Thu, 02 Jun 2016 20:40:53 -0400
Date: Fri, 3 Jun 2016 08:40:48 +0800
From: Fam Zheng <famz@redhat.com>
Message-ID: <20160603004048.GA29298@ad.usersys.redhat.com>
References: <1464850102-17829-1-git-send-email-jasowang@redhat.com>
	<CAFEAcA_Z=XFYisQmAb5Nmh54LmdQ_cae10vyH6sDYvAdKtBz0g@mail.gmail.com>
	<CAFEAcA_fK_gEjVo58+NVVH5ukJTd+M_aXt9z1Z6Dqdi7zoBScQ@mail.gmail.com>
	<34D97F73-5DF1-4C15-B7B8-C7A947E17E88@daynix.com>
	<5750837C.7030900@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5750837C.7030900@redhat.com>
Subject: Re: [Qemu-devel] [PULL V4 00/31] Net patches
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: Eric Blake <eblake@redhat.com>
Cc: Dmitry Fleytman <dmitry@daynix.com>, Peter Maydell <peter.maydell@linaro.org>, Jason Wang <jasowang@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>

On Thu, 06/02 13:05, Eric Blake wrote:
> On 06/02/2016 12:09 PM, Dmitry Fleytman wrote:
> 
> > 
> > The build did not pass because of tracepoint e1000e_rx_rss_ip6 which failed to compile.
> > 
> > This tracepoint has 11 parameters, when 1 parameter is removed build succeeds.
> > Could it be that ust backend has a limitation of 10 parameters per event?
> > Should I split this trace into 2 events?
> > 
> > In general, I would like to check compilability of my patches better next time,
> > is there a way to figure out a full list of configurations to be tested? Is there a tool for that maybe?
> 
> The brand new docker tests (see commit cbd614870 and above) should make
> it easier to test multiple setups, although I'm not sure if ust is one
> of the docker tests yet.

Yes, thanks for mentioning! And there is a "travis" script that can mimic
travis-ci.org testing (it's a PoC far from perfect for now):

    make docker-travis@ubuntu

Next step, I'll take a look at our .travis.yml matrix and make a selection out
of that (maybe by flattening all dimensions onto one base configuration, so it
can become a first class test that completes in a resonable time on a single
average machine that a developer owns).

Fam