From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) by dpdk.org (Postfix) with ESMTP id 7EB3C2C27 for ; Thu, 13 Apr 2017 08:46:08 +0200 (CEST) Received: by mail-wm0-f54.google.com with SMTP id o81so103589376wmb.1 for ; Wed, 12 Apr 2017 23:46:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=dQ/yu4VgJNLdiTdBr7wiOCROkoMdSiH3EnYRTGD8sIs=; b=MOA6jhpzCWMei0B9kGL3snaKVaJZfXippw8MDWi3C5E4cNPxSVYHG9vcREm1jbUvP6 nU8wthld9EP9MDRMItB/4Aaj/OtedfjH5Y+xBVcw1eFDbmT3BgXI0B08ET8/RpVaCdUY bODebv5c3ZTqYCY+rLxmk7/BHzyB7KLukGLdtYzNjC13aJ9s4kBTqaRMrAhakJ/M8zEK 8xKddizxzJQUtrHX3qz2amnASfMFch/7cmz6ZWaiJ+9clzWvrZWP7L9dK8TDylKgBCju NIjSu6mOobBEzS1pgelFwHsdv4OsFUVUr9mkpkMrg8fDtgX2KIPRL/7SY3j8+n8NGTJb 7Z1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=dQ/yu4VgJNLdiTdBr7wiOCROkoMdSiH3EnYRTGD8sIs=; b=e5UA+vUNXqJyoZIliLxQ2w0KgRmKrdObUvNiuA+fara/1gjY3NPSc2lSrNx6Biiik7 9e4FB8Pwuy1wotUS7vG0JSRaS+4987d0JayalEMYAjSK+lKdSDqfdoaouc/0ykvOQ6TC Uz8hnf/TkxNweLIHzCeE+O7Dwp28LTtbXyHcdB3X5maG8w9Erq/L4iYMF3bA9ZQ7Y6n5 tRBPFeMOvk5Ggym5Pm/G6n8+jgBftxc7/E/ERwFuTQBI1YEqawn2YJRhjmZwU/1C0XM/ oogYzyhq8IifPtRjG7XI887oPBN+76PCl1ekPKmXtG79sLMMyk2s5CVSZEPaBhYCUDdk bJZg== X-Gm-Message-State: AN3rC/6Ahnk+Edux0FUeQrXm+ko/UxG5RtjkggWFxe5VOtwmoRYlrREk o6A8tdejAUwiL1I8 X-Received: by 10.28.127.139 with SMTP id a133mr1785793wmd.84.1492065968276; Wed, 12 Apr 2017 23:46:08 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id f6sm4289195wrf.13.2017.04.12.23.46.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Apr 2017 23:46:07 -0700 (PDT) From: Thomas Monjalon To: "Xu, Qian Q" Cc: ci@dpdk.org, "Richardson, Bruce" Date: Thu, 13 Apr 2017 08:46:06 +0200 Message-ID: <6814152.1hysv1icOi@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E3B5C7B6C@shsmsx102.ccr.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA722C837C@IRSMSX108.ger.corp.intel.com> <1564461.MHdNEdeViC@xps13> <82F45D86ADE5454A95A89742C8D1410E3B5C7B6C@shsmsx102.ccr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: Thu, 13 Apr 2017 06:46:08 -0000 2017-04-13 05:25, Xu, Qian Q: > To do the per patchset performance test, we need to know that the patchset's target repo. Any thoughts here? 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 Later it would be a good idea to store the rules in the dpdk repo near the file MAINTAINERS, so patchwork could parse them and display the maintainers and the tree for the patches. > > -----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 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.