From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 95C03316B for ; Thu, 13 Apr 2017 07:27:35 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Apr 2017 22:27:34 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,193,1488873600"; d="scan'208";a="1118910159" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga001.jf.intel.com with ESMTP; 12 Apr 2017 22:27:33 -0700 Received: from FMSMSX110.amr.corp.intel.com (10.18.116.10) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 12 Apr 2017 22:25:53 -0700 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by fmsmsx110.amr.corp.intel.com (10.18.116.10) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 12 Apr 2017 22:25:53 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.246]) by SHSMSX104.ccr.corp.intel.com ([10.239.4.70]) with mapi id 14.03.0319.002; Thu, 13 Apr 2017 13:25:51 +0800 From: "Xu, Qian Q" To: "ci@dpdk.org" CC: "Richardson, Bruce" , "Xu, Qian Q" , Thomas Monjalon Thread-Topic: DPDK Lab Thread-Index: AdKSmrSzk1TvaKevQQ6Ly5HnPaS8pgbN9nhwABA9R3AAJQm6EAAEwSaQ//+bOQD/9OSjQA== Date: Thu, 13 Apr 2017 05:25:51 +0000 Message-ID: <82F45D86ADE5454A95A89742C8D1410E3B5C7B6C@shsmsx102.ccr.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA722C837C@IRSMSX108.ger.corp.intel.com> <82F45D86ADE5454A95A89742C8D1410E3B5BA2BB@shsmsx102.ccr.corp.intel.com> <1564461.MHdNEdeViC@xps13> In-Reply-To: <1564461.MHdNEdeViC@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] 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 05:27:36 -0000 To do the per patchset performance test, we need to know that the patchset'= s target repo. Any thoughts here?=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 JARDI= N' > ; Guillaume Gaudonville > ; Shreyansh Jain > ; 'Kevin Traynor' > Subject: Re: DPDK Lab >=20 > 2017-04-06 09:57, Xu, Qian Q: > > As to the per patchset performance test, as you know, there are many re= pos > 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 fin= d 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? >=20 > For most of the patches it should be obvious to determine the targetted r= epo. > 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.