DPDK CI discussions
 help / color / mirror / Atom feed
From: "Wei, FangfangX" <fangfangx.wei@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Xu, Qian Q" <qian.q.xu@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, "Liu, Yong" <yong.liu@intel.com>
Subject: Re: [dpdk-ci] Intel PerPatch Build
Date: Thu, 1 Dec 2016 09:29:56 +0000	[thread overview]
Message-ID: <067B569323FEB248B5CB480E1954F4346BE9143F@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <3298229.S52HG4ql9W@xps13>

Hi Thomas,

Sorry for the late reply, I was working on other tasks these days, and will start to try your scripts ASAP.

Best Regards
Fangfang Wei

-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] 
Sent: Thursday, December 1, 2016 5:27 PM
To: Xu, Qian Q <qian.q.xu@intel.com>
Cc: ci@dpdk.org; Wei, FangfangX <fangfangx.wei@intel.com>; Liu, Yong <yong.liu@intel.com>
Subject: Re: Intel PerPatch Build

2016-12-01 09:00, Xu, Qian Q:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > 2016-11-30 09:25, Xu, Qian Q:
> > > Then the conclusion is that we just kept current model, 1 report for 1 patch,
> > right?
> > 
> > Yes
> > Thanks for the discussion
> > (I keep this discussion in mind in case it needs some improvement)
> > 
> > > Also keep in mind some things about the error comparison, we can discuss it
> > again if we see many these issues.
> > 
> > Yes
> > 
> > > As to the next step, I think Fangfang can check how to update the per patch
> > build result to the patchwork to make the result more visible/readable in website.
> > 
> > Yes please.
> > I'm also waiting to apply the patches. Should I apply them right now?
> > 
> Do you mean your script patches? I think fangfang may give some comments here. 

Yes please

      reply	other threads:[~2016-12-01  9:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <587443$9qu68@orsmga002.jf.intel.com>
2016-11-28  7:30 ` [dpdk-ci] [dpdk-test-report] [Intel PerPatch Build] |SUCCESS| pw17274 [PATCH, v2] maintainers: update testpmd maintainer Xu, Qian Q
2016-11-28 10:08   ` [dpdk-ci] Intel PerPatch Build Thomas Monjalon
2016-11-29  3:56     ` Xu, Qian Q
2016-11-29  9:20       ` Thomas Monjalon
2016-11-30  6:49         ` Xu, Qian Q
2016-11-30  8:33           ` Thomas Monjalon
2016-11-30  9:25             ` Xu, Qian Q
2016-11-30  9:46               ` Thomas Monjalon
2016-12-01  9:00                 ` Xu, Qian Q
2016-12-01  9:26                   ` Thomas Monjalon
2016-12-01  9:29                     ` Wei, FangfangX [this message]

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=067B569323FEB248B5CB480E1954F4346BE9143F@SHSMSX101.ccr.corp.intel.com \
    --to=fangfangx.wei@intel.com \
    --cc=ci@dpdk.org \
    --cc=qian.q.xu@intel.com \
    --cc=thomas.monjalon@6wind.com \
    --cc=yong.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).