From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Peng, Yuan" <yuan.peng@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 20.02-rc3
Date: Thu, 20 Feb 2020 10:56:57 +0100 [thread overview]
Message-ID: <b0522e0f-268c-b3a1-0199-2ea2e1ffdf93@redhat.com> (raw)
In-Reply-To: <67D543A150B29E4CAAE53918F64EDAEA37802BE4@SHSMSX103.ccr.corp.intel.com>
Hi,
Thanks for the testing.
On 2/20/20 10:41 AM, Peng, Yuan wrote:
> DPDK 20.02 RC3 Test Report from intel:
>
> Summary
> • Totally 9898 test cases for 20.02 RC3, 9629 cases are executed, 9428 test cases passed, 178 test cases failed, 23 test case blocked, Execution rate is 97.28%, pass rate is 97.91%.
> • Totally create ~278 new tests for DPDK20.02 new features.
> • New to create 9 issues from STV in RC3 till now, not include some issues have found and reported before RC3.
> • Met 1 build issue on Centos 7.4 with DPDK 20.02 RC3, now it has been fixed, and patch applied.
> Details:
> • Intel NIC PMD PF & VF regression: 99% executed, 0 critical issue and 1 high issue is tracked(verified).
> Function cases include rx/tx/forward packets, packet processing, jumboframe, dual vlan, filter cases and so on: 5 bugs found, no critical and high level.
> Performance cases such as l2fwd, l3fwd, single core and so on: no new bug is found.
> • Crypto cases include ipsec_gw cryptodev, fips cryptodev, l2fwd crypto, performance cases and so on: no critical and no high bugs found.
> • Vhost/virtio: PVP/loopback, qemu/virtio-user, multi-queue, dequeue zero copy cases and so on: 1 new medium bug is found.
Do you confirm this is the bug we fixed earlier this week thqt
reproduced in Vhost PMD when stop and starting port?
Maxime
prev parent reply other threads:[~2020-02-20 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 21:58 Thomas Monjalon
2020-02-19 13:12 ` Pei Zhang
2020-02-20 9:41 ` Peng, Yuan
2020-02-20 9:56 ` Maxime Coquelin [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=b0522e0f-268c-b3a1-0199-2ea2e1ffdf93@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--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).