[dpdk-ci] DPDK Lab

[Richardson, Bruce]

Majority (90%) of the time, the subject prefix on the patches should provide 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 automatically determine the tree, but those patchset should perhaps have delayed 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 at dpdk.org
> Cc: Richardson, Bruce <bruce.richardson at intel.com>; Xu, Qian Q
> <qian.q.xu at intel.com>; Thomas Monjalon <thomas.monjalon at 6wind.com>
> Subject: RE: DPDK Lab
> 
> To do the per patchset performance test, we need to know that the
> patchset's target repo. Any thoughts here?
> 
> 
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> > Sent: Thursday, April 6, 2017 7:46 PM
> > To: Xu, Qian Q <qian.q.xu at intel.com>
> > Cc: Erez Scop <erezsc at mellanox.com>; O'Driscoll, Tim
> > <tim.odriscoll at intel.com>; Liu, Yong <yong.liu at intel.com>; 'Vincent
> JARDIN'
> > <vincent.jardin at 6wind.com>; Guillaume Gaudonville
> > <Guillaume.Gaudonville at 6wind.com>; Shreyansh Jain
> > <shreyansh.jain at nxp.com>; 'Kevin Traynor' <ktraynor at redhat.com>
> > 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 at dpdk.org.