[dpdk-ci] [PATCH v4] add script to decide best tree match for patches

[Jeremy Plsek]

On Fri, Apr 19, 2019 at 1:55 PM Thomas Monjalon <thomas at monjalon.net> wrote:
>
> 19/04/2019 19:33, Jeremy Plsek:
> > I thinks so. Only more patchsets will tell, but that could be improved
> > after the fact. So I think it's fine to merge it in.
> >
> > At first glance, the only part that I don't think is implemented is
> > mentioned here: https://bugs.dpdk.org/show_bug.cgi?id=166#c35
> > > We must match the common prefix of the git trees.
> > > Examples:
> > > dpdk-next-net-intel + dpdk = dpdk
> > > dpdk-next-net-intel + dpdk-next-net-mlx = dpdk-next-net
> > Since some of the patches are being set to dpdk-next-net-mlx instead
> > of dpdk-next-net. But I'm fine with how it is right now and wouldn't
> > mind it getting changed to this later on.
>
> It is supposed to be fixed.
> Please could you give an example of a misbehaviour?

The most recent example is series 4380. For me, that returned dpdk-next-net-mlx.

> PS: please avoid top-post, it is making thread hard to read.

Sure. It would be great if it wasn't the default for Gmail ;)

>
> > On Fri, Apr 19, 2019 at 12:24 PM Thomas Monjalon <thomas at monjalon.net> wrote:
> > >
> > > 19/04/2019 18:21, Jeremy Plsek:
> > > > On Thu, Apr 18, 2019 at 4:16 AM Ali Alnubani <alialnu at mellanox.com> wrote:
> > > > > Did you guys get a chance to test this version?
> > > >
> > > > We've switched to using it a few days ago.
> > > > Some examples of it switching branches:
> > > > https://lab.dpdk.org/results/dashboard/patchsets/5503/
> > > > https://lab.dpdk.org/results/dashboard/patchsets/5499/
> > > > https://lab.dpdk.org/results/dashboard/patchsets/5498/
> > >
> > > Is it working as you expect?
> > > May I merge it in dpdk-ci?
>
>
>
>
>


-- 
Jeremy Plsek
UNH InterOperability Laboratory