From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id B19592BA2 for ; Tue, 25 Apr 2017 08:23:37 +0200 (CEST) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Apr 2017 23:23:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,248,1488873600"; d="scan'208";a="91808450" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by orsmga005.jf.intel.com with ESMTP; 24 Apr 2017 23:23:35 -0700 Received: from fmsmsx125.amr.corp.intel.com (10.18.125.40) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 24 Apr 2017 23:23:35 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by FMSMSX125.amr.corp.intel.com (10.18.125.40) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 24 Apr 2017 23:23:35 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.246]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.193]) with mapi id 14.03.0319.002; Tue, 25 Apr 2017 14:23:33 +0800 From: "Xu, Qian Q" To: Thomas Monjalon CC: "ci@dpdk.org" , "Richardson, Bruce" , "Wei, FangfangX" , "O'Driscoll, Tim" , "Liu, Yuanhan" , "Xu, Qian Q" Thread-Topic: script to determine target repo (was DPDK Lab) Thread-Index: AQHStCGuVaJiVBER0kWSfXBHnGYchKHVrwQw Date: Tue, 25 Apr 2017 06:23:32 +0000 Message-ID: <82F45D86ADE5454A95A89742C8D1410E3B5DE563@shsmsx102.ccr.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA722C837C@IRSMSX108.ger.corp.intel.com> <1564461.MHdNEdeViC@xps13> <82F45D86ADE5454A95A89742C8D1410E3B5C7B6C@shsmsx102.ccr.corp.intel.com> <6814152.1hysv1icOi@xps13> In-Reply-To: <6814152.1hysv1icOi@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] script to determine target repo (was 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: Tue, 25 Apr 2017 06:23:38 -0000 Thanks Thomas and Bruce for your comments. Currently we are trying to start= the per patch set performance test investigation and need to know the=20 Target repo for each patch set. =20 The goal is to get 100% correct repo to go for each patch set. It's importa= nt for the credit of the performance result.=20 @Thomas, could you provide any script to support the auto-filter after the = 17.05 release? Currently, we don't have the ability to make it.=20 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Thursday, April 13, 2017 2:46 PM > To: Xu, Qian Q > Cc: ci@dpdk.org; Richardson, Bruce > Subject: Re: script to determine target repo (was DPDK Lab) >=20 > 2017-04-13 05:25, Xu, Qian Q: > > To do the per patchset performance test, we need to know that the patch= set's > target repo. Any thoughts here? >=20 > The first task is to extract modified files from lines starting with +++. > Then we must apply some basic rules. > Example: if every paths start with > drivers/crypto/ > or lib/librte_cryptodev/ > or doc/guides/cryptodevs/ > then it goes to dpdk-next-crypto >=20 > Later it would be a good idea to store the rules in the dpdk repo near th= e file > MAINTAINERS, so patchwork could parse them and display the maintainers an= d > the tree for the patches. >=20 >=20 > > > -----Original Message----- > > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > > Sent: Thursday, April 6, 2017 7:46 PM > > > > > > 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 did= n't > work. > > > > Any comments here? > > > > > > For most of the patches it should be obvious to determine the targett= ed repo. > > > We should add a script in dpdk-ci to get the repo name from a patchse= t. > > > Anyway, this technical discussion should be on ci@dpdk.org. >=20