From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 7243E2C27 for ; Thu, 13 Apr 2017 10:24:34 +0200 (CEST) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga104.jf.intel.com with ESMTP; 13 Apr 2017 01:24:33 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,194,1488873600"; d="scan'208";a="88599912" Received: from irsmsx109.ger.corp.intel.com ([163.33.3.23]) by fmsmga006.fm.intel.com with ESMTP; 13 Apr 2017 01:24:32 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.241]) by IRSMSX109.ger.corp.intel.com ([169.254.13.12]) with mapi id 14.03.0319.002; Thu, 13 Apr 2017 09:24:31 +0100 From: "Richardson, Bruce" To: "Xu, Qian Q" , "ci@dpdk.org" CC: Thomas Monjalon Thread-Topic: DPDK Lab Thread-Index: AdKSmrSzk1TvaKevQQ6Ly5HnPaS8pgbN9nhwABA9R3AAJQm6EAAEwSaQ//+bOQD/9OSjQP/plznA Date: Thu, 13 Apr 2017 08:24:30 +0000 Message-ID: <59AF69C657FD0841A61C55336867B5B066756B75@IRSMSX103.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA722C837C@IRSMSX108.ger.corp.intel.com> <82F45D86ADE5454A95A89742C8D1410E3B5BA2BB@shsmsx102.ccr.corp.intel.com> <1564461.MHdNEdeViC@xps13> <82F45D86ADE5454A95A89742C8D1410E3B5C7B6C@shsmsx102.ccr.corp.intel.com> In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E3B5C7B6C@shsmsx102.ccr.corp.intel.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZTVjNWE0Y2QtNWQ2MC00MDRhLTk2ZGQtN2EwMDkzMmJjN2ZkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6IlhEXC9DNUtMMkhpeVV6MTZtcFNHYVBYVmRhVU9Ec1wveWVLeWVoQklXaDZxUT0ifQ== x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-ci] DPDK Lab X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2017 08:24:35 -0000 Majority (90%) of the time, the subject prefix on the patches should provid= e the hint. If the majority of the patches start with "net/" then it's for = next-net, and similarly for crypto. Patches with virtio or vhost go to that= tree, etc. There will be edge cases where we get it wrong or just can't au= tomatically determine the tree, but those patchset should perhaps have dela= yed checking after we have manual assignment of tree. What could also work = in those cases is to wait to scan them until we get a delegate assigned in = patchwork, as that will tell us what tree they are to hit. /Bruce > -----Original Message----- > From: Xu, Qian Q > Sent: Thursday, April 13, 2017 6:26 AM > To: ci@dpdk.org > Cc: Richardson, Bruce ; Xu, Qian Q > ; Thomas Monjalon > Subject: RE: DPDK Lab >=20 > To do the per patchset performance test, we need to know that the > patchset's target repo. Any thoughts here? >=20 >=20 > > -----Original Message----- > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > Sent: Thursday, April 6, 2017 7:46 PM > > To: Xu, Qian Q > > Cc: Erez Scop ; O'Driscoll, Tim > > ; Liu, Yong ; 'Vincent > JARDIN' > > ; Guillaume Gaudonville > > ; Shreyansh Jain > > ; 'Kevin Traynor' > > Subject: Re: DPDK Lab > > > > 2017-04-06 09:57, Xu, Qian Q: > > > As to the per patchset performance test, as you know, there are many > > > repos > > for DPDK now, so when a new patchset coming, which repo should it go to= ? > > Maybe it doesn't go to dpdk master, but go to dpdk-next-virtio, or > > others, but automation tool doesn't know that. > > > As to per patch build, we are trying the patch on different repo to > > > find the one > > that can pass build, but as to performance test for per patchset, we > > must apply the patchset into correct repo/branch or else the code didn'= t > work. > > > Any comments here? > > > > For most of the patches it should be obvious to determine the targetted > repo. > > We should add a script in dpdk-ci to get the repo name from a patchset. > > Anyway, this technical discussion should be on ci@dpdk.org.