From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "ci@dpdk.org" <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>
Subject: Re: [dpdk-ci] script to determine target repo (was DPDK Lab)
Date: Tue, 25 Apr 2017 06:24:55 +0000 [thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E3B5DE5EB@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E3B5DE563@shsmsx102.ccr.corp.intel.com>
Sent to correct Thomas' mail:), Thomas, could you see below? Thx.
> -----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.
> >
next prev parent reply other threads:[~2017-04-25 6:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26FA93C7ED1EAA44AB77D62FBE1D27BA722C837C@IRSMSX108.ger.corp.intel.com>
[not found] ` <HE1PR0501MB21370D6ACD0931D36925D085BD0D0@HE1PR0501MB2137.eurprd05.prod.outlook.com>
[not found] ` <82F45D86ADE5454A95A89742C8D1410E3B5BA2BB@shsmsx102.ccr.corp.intel.com>
[not found] ` <1564461.MHdNEdeViC@xps13>
2017-04-13 5:25 ` [dpdk-ci] DPDK Lab Xu, Qian Q
2017-04-13 6:46 ` [dpdk-ci] script to determine target repo (was DPDK Lab) Thomas Monjalon
2017-04-25 6:23 ` Xu, Qian Q
2017-04-25 6:24 ` Xu, Qian Q [this message]
2017-04-25 6:37 ` Wei, FangfangX
2017-04-25 6:41 ` Wei, FangfangX
2017-04-25 6:48 ` Thomas Monjalon
2017-04-25 6:50 ` Thomas Monjalon
2017-06-21 7:45 ` Wei, FangfangX
2017-06-21 8:20 ` Richardson, Bruce
2017-06-21 8:33 ` Thomas Monjalon
2017-06-23 8:43 ` Xu, Qian Q
2017-06-23 9:30 ` Richardson, Bruce
2017-06-26 3:47 ` Xu, Qian Q
2017-06-26 6:23 ` Jerin Jacob
2017-06-26 13:26 ` Xu, Qian Q
2017-06-30 8:41 ` Wei, FangfangX
2017-06-30 9:22 ` Thomas Monjalon
2017-04-13 8:24 ` [dpdk-ci] DPDK Lab Richardson, Bruce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82F45D86ADE5454A95A89742C8D1410E3B5DE5EB@shsmsx102.ccr.corp.intel.com \
--to=qian.q.xu@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=fangfangx.wei@intel.com \
--cc=thomas@monjalon.net \
--cc=tim.odriscoll@intel.com \
--cc=yuanhan.liu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).