From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Liu, Yong" <yong.liu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] dpdk pre-patch testing introduction
Date: Thu, 29 Oct 2015 17:30:37 +0100 [thread overview]
Message-ID: <22607203.7fcSgJEPLE@xps13> (raw)
In-Reply-To: <86228AFD5BCD8E4EBFD2B90117B5E81E10F379B0@SHSMSX103.ccr.corp.intel.com>
2015-10-29 15:19, Liu, Yong:
> So far, we only enabled one platform to run automatic testing.
> This platform installed Fedora 20 with Linux 3.18.9 and Intel Niantic NIC.
Thanks for offering this service.
> Currently the patch testing only run unit test and basic function test on this platform.
> It can make sure that new patch doesn't break original code and functions.
> Due to coverage limitation, it can't verify the functionality of new patch.
> If you want to verify your patch's new function, you need to check with tester and perform specific testing on it.
>
> Since platform limitation, we are not able to verify regression test on other NIC, Linux kernel.
> We plan to add more platforms and support different NIC and kernels in the future.
The mailing list for test report is open to others.
Submitters are white-listed.
Feel free to contribute with your own tests on your own platform.
Some work is ongoing to track the test results from patchwork.
https://lists.ozlabs.org/pipermail/patchwork/2015-July/001363.html
https://lists.ozlabs.org/pipermail/patchwork/2015-July/001369.html
next prev parent reply other threads:[~2015-10-29 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 15:19 Liu, Yong
2015-10-29 16:30 ` Thomas Monjalon [this message]
2015-11-02 7:54 ` Simon Kågström
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=22607203.7fcSgJEPLE@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--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).