From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Cao, Waterman" <waterman.cao@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] patches validation
Date: Thu, 25 Sep 2014 23:29:41 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB9772582137AB66@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <1636341.y1s87QthrV@xps13>
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Thursday, September 25, 2014 4:05 PM
> To: Cao, Waterman
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] patches validation
>
> 2014-09-25 13:07, Cao, Waterman:
> > I will work with team to see if we can improve test report.
> > Because intel validation team will continue to upgrade test cases to verify feature,
> > I think that it's still worth to verify patch or features even it has already integrated branch.
>
> Of course, it's important to continue validation after integration.
> But please do not send test report on the list for patches which are
> already integrated, except for 2 cases:
> 1) there is an error
> 2) this is a new feature and you want to explain how to test it
> (btw, how do you test "zero copy" and "one copy" for virtio?)
>
> About report content, please add these informations:
> - commit id or tag used as a base to apply the patch
> - tools used for the test (testpmd, sample, qemu, etc)
> - command parameters if relevant
> - test topology if relevant
>
> If someone think about an useful information I missed, please share it.
May be it is just me, but what's wrong with mail for every tested patch?
At least it makes easy to check was the patch formally validated or not - all you have to do - grep through mail archives.
Konstantin
> We could write some guidelines for test and bug reports and publish it
> on the website. Drafts are welcome.
>
> Thanks
> --
> Thomas
next prev parent reply other threads:[~2014-09-25 23:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 10:55 [dpdk-dev] [PATCH] ixgbe: fix compile error with gcc4.4 (used RHEL 6) Bruce Richardson
2014-09-18 11:09 ` Thomas Monjalon
2014-09-18 12:25 ` Neil Horman
2014-09-18 12:35 ` Richardson, Bruce
2014-09-18 15:03 ` Neil Horman
2014-09-18 15:16 ` Bruce Richardson
2014-09-18 15:46 ` Neil Horman
2014-09-18 15:38 ` Thomas Monjalon
2014-09-18 15:50 ` Neil Horman
2014-09-18 16:01 ` Richardson, Bruce
2014-09-18 18:12 ` Neil Horman
2014-09-25 2:13 ` Tang, HaifengX
2014-09-25 7:02 ` Thomas Monjalon
2014-09-25 13:07 ` Cao, Waterman
2014-09-25 15:05 ` [dpdk-dev] patches validation Thomas Monjalon
2014-09-25 23:29 ` Ananyev, Konstantin [this message]
2014-09-26 9:23 ` Thomas Monjalon
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=2601191342CEEE43887BDE71AB9772582137AB66@IRSMSX104.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=waterman.cao@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).