Re: [dpdk-ci] script to determine target repo (was DPDK Lab)

["Wei, FangfangX" <fangfangx.wei@intel.com>]

Hi Thomas,
Another question need your help: How I can auto-filter the patchset which include some patches?
Currently we filter the patchset with the format 'Message-Id: <([0-9-]+)-git-send-email-.*@.*>' in per-patch build testing system. But I find that there are some different format about the message-id, such as " 20170420072402.38106-5-aik@ozlabs.ru", "1492658865-30077-1-git-send-email-wei.zhao1@intel.com", "20170209165959.28082-3-benjamin.walker@intel.com", " 3da244231b6868ccc3e70d91dc277df39a3695bd.1481592081.git.mirq-linux@rere.qmqm.pl" and etc.


Best Regards
Fangfang Wei

-----Original Message-----
From: Xu, Qian Q 
Sent: Tuesday, April 25, 2017 2:24 PM
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: ci@dpdk.org; Richardson, Bruce <bruce.richardson@intel.com>; Wei, FangfangX <fangfangx.wei@intel.com>; O'Driscoll, Tim <tim.odriscoll@intel.com>; Liu, Yuanhan <yuanhan.liu@intel.com>; Xu, Qian Q <qian.q.xu@intel.com>
Subject: RE: script to determine target repo (was DPDK Lab)

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 Target repo for each patch set.  
The goal is to get 100% correct repo to go for each patch set. It's important for the credit of the performance result. 
@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. 

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Thursday, April 13, 2017 2:46 PM
> To: Xu, Qian Q <qian.q.xu@intel.com>
> Cc: ci@dpdk.org; Richardson, Bruce <bruce.richardson@intel.com>
> Subject: Re: script to determine target repo (was DPDK Lab)
> 
> 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.
>