From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: Ali Alnubani <alialnu@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Raslan Darawsheh <rasland@mellanox.com>,
Asaf Penso <asafp@mellanox.com>,
"Peng, Yuan" <yuan.peng@intel.com>,
"Yu, PingX" <pingx.yu@intel.com>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 20.02-rc4
Date: Tue, 25 Feb 2020 14:37:08 +0000 [thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E407A4194@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <AM0PR05MB4401E36A90059B2C24155505D7ED0@AM0PR05MB4401.eurprd05.prod.outlook.com>
Some quick update from Intel on RC4 testing
Summary
1. Totally execution percentage is around 90%, pass rate is around 98%
2. Created 2 new medium/low issue in RC4.
Details:
1. Intel NIC PMD PF & VF regression: 95% executed, 0 critical issue and high issue found.
Function cases include rx/tx/forward packets, packet processing, jumboframe, dual vlan, filter cases and so on: 2 bugs found, no critical/high bugs.
Performance cases such as l2fwd, l3fwd, single core and so on: no new bug is found.
2. Cryptodev cases include ipsec_gw cryptodev, fips cryptodev, l2fwd crypto, performance cases and so on: no critical and no high bugs found.
Function cases all passed, performance cases not fully executed.
3. Vhost/virtio: PVP/loopback, qemu/virtio-user, multi-queue, dequeue zero copy cases and so on: 1 new medium bug is found.
4. Power relate cases, no new bug is found.
5. ABI test includes unit test, vhost and flow related tests. no new bug is found.
6. 20.02 new features include ABI test, L2tpv3, crypto_dev related new features and so no. no new bug is found.
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Ali Alnubani
> Sent: Tuesday, February 25, 2020 5:59 PM
> To: Thomas Monjalon <thomas@monjalon.net>; dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@mellanox.com>; Asaf Penso
> <asafp@mellanox.com>
> Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 20.02-rc4
>
> Hi,
>
> > -----Original Message-----
> > From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas
> > Monjalon
> > Sent: Saturday, February 22, 2020 11:08 PM
> > To: announce@dpdk.org
> > Subject: [dpdk-announce] release candidate 20.02-rc4
> >
> > A new DPDK release candidate is ready for testing:
> <removed>
> >
> > This is the last release candidate for DPDK 20.02.
> > Please share some release validation results by replying to this
> > message (at dev@dpdk.org).
> > If no critical issue is reported, 20.02 will be closed on Tuesday 25th.
> >
> > If you are preparing the next release cycle, please send your v1
> > patches before the 20.05 proposal deadline, which will happen on March 18th.
> > It is also time to build an estimated roadmap for the next cycles.
> >
> > Thank you everyone
> >
>
> The following covers the tests that we ran on Mellanox hardware for this
> version:
>
> - Basic functionality:
> Send and receive multiple types of traffic.
> - testpmd xstats counter test.
> - testpmd timestamp test.
> - Changing/checking link status through testpmd.
> - RTE flow and flow_director tests.
> Items: eth / vlan / ipv4 / ipv6 / tcp / udp / icmp / gre / nvgre / vxlan / geneve /
> ip in ip / mplsoudp / mplsogre / gtp
> Actions: drop / queue / rss / mark / flag / jump / count / port_id / raw_encap /
> raw_decap / vxlan_encap / vxlan_decap / NAT
> - Some RSS tests.
> - VLAN stripping and insertion tests.
> - Checksum and TSO tests.
> - ptype tests.
> - l3fwd-power example application tests.
> - Multi-process example applications tests.
>
> We don't see any critical issues blocking the release.
>
> Thanks,
> Ali
next prev parent reply other threads:[~2020-02-25 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 21:08 Thomas Monjalon
2020-02-25 9:58 ` Ali Alnubani
2020-02-25 14:37 ` Xu, Qian Q [this message]
2020-02-25 14:44 ` Thomas Monjalon
2020-02-25 15:27 ` Raslan Darawsheh
2020-03-18 0:54 ` [dpdk-dev] [EXTERNAL] " Abhishek Marathe
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=82F45D86ADE5454A95A89742C8D1410E407A4194@shsmsx102.ccr.corp.intel.com \
--to=qian.q.xu@intel.com \
--cc=alialnu@mellanox.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=pingx.yu@intel.com \
--cc=rasland@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yuan.peng@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).