From: Luca Boccassi <Luca.Boccassi@microsoft.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 19.11-rc4
Date: Thu, 28 Nov 2019 09:51:10 +0000 [thread overview]
Message-ID: <257c086cee51c1ddba6dbf907d8cabd2a2500b0e.camel@microsoft.com> (raw)
In-Reply-To: <2848553.yd9UBBcNlK@xps>
Hi,
Here's the report from the automated Jenkins pipeline at MSFT - QA team
will be out for Thanksgiving this week, they can chip in next week for
more details, but I do not see any blocking issue being highlighted -
just the usual small performance issue that is already being
investigated separately.
DPDK v19.11-rc4 was validated on Azure for Canonical UbuntuServer 16.04-LTS latest, Canonical UbuntuServer 18.04-DAILY-LTS latest, RedHat RHEL 7-RAW latest, RedHat RHEL 7.5 latest, Openlogic CentOS 7.5 latest, SUSE SLES 15 latest.
Tested with Mellanox and netvsc poll-mode drivers.
The tests were executed using LISAv2 framework ( https://github.com/LIS/LISAv2 ).
Test case description:
* VERIFY-DPDK-COMPLIANCE - verifies kernel is supported and that the build is successful
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST - verifies using testpmd that packets can be sent from a VM to another VM
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK - disables/enables Accelerated Networking for the NICs under test and makes sure DPDK works in both scenarios
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC - disables/enables Accelerated Networking for the NICs while generating traffic using testpmd
* PERF-DPDK-FWD-PPS-DS15 - verifies DPDK forwarding performance using testpmd on 2, 4, 8 cores, rx and io mode on size Standard_DS15_v2
* PERF-DPDK-SINGLE-CORE-PPS-DS4 - verifies DPDK performance using testpmd on 1 core, rx and io mode on size Standard_DS4_v2
* PERF-DPDK-SINGLE-CORE-PPS-DS15 - verifies DPDK performance using testpmd on 1 core, rx and io mode on size Standard_DS15_v2
* PERF-DPDK-MULTICORE-PPS-DS15 - verifies DPDK performance using testpmd on 2, 4, 8 cores, rx and io mode on size Standard_DS15_v2
* PERF-DPDK-MULTICORE-PPS-F32 - verifies DPDK performance using testpmd on 2, 4, 8, 16 cores, rx and io mode on size Standard_F32s_v2
* DPDK-RING-LATENCY - verifies DPDK CPU latency using https://github.com/shemminger/dpdk-ring-ping
* VERIFY-DPDK-PRIMARY-SECONDARY-PROCESSES - verifies primary / secondary processes support for DPDK. Runs only on RHEL and Ubuntu distros with Linux kernel >= 4.20
* VERIFY-DPDK-OVS - builds OVS with DPDK support and tests if the OVS DPDK ports can be created. Runs only on Ubuntu distro.
* VERIFY-DPDK-VPP - builds VPP with DPDK support and tests if the VPP ports are present. Runs only on RHEL and Ubuntu distros.
* VERIFY-DPDK-NFF-GO - builds NFF-GO with DPDK support and runs the functional tests from the NFF-GO repository. Runs only on Ubuntu distro.
DPDK job exited with status: UNSTABLE.
Test results for DPDK 'v19.11-rc4' and Azure image: 'Canonical UbuntuServer 16.04-LTS latest':
* PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED
* VERIFY-DPDK-OVS: PASSED
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
* PERF-DPDK-MULTICORE-PPS-F32: PASSED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
Test results for DPDK 'v19.11-rc4' and Azure image: 'Canonical UbuntuServer 18.04-DAILY-LTS latest':
* PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
* VERIFY-DPDK-OVS: PASSED
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
* PERF-DPDK-MULTICORE-PPS-F32: FAILED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
Test results for DPDK 'v19.11-rc4' and Azure image: 'RedHat RHEL 7-RAW latest':
* PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
* VERIFY-DPDK-OVS: SKIPPED
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
* PERF-DPDK-MULTICORE-PPS-F32: FAILED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
Test results for DPDK 'v19.11-rc4' and Azure image: 'RedHat RHEL 7.5 latest':
* PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
* VERIFY-DPDK-OVS: SKIPPED
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
* PERF-DPDK-MULTICORE-PPS-F32: PASSED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
Test results for DPDK 'v19.11-rc4' and Azure image: 'Openlogic CentOS 7.5 latest':
* PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
* VERIFY-DPDK-OVS: SKIPPED
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
* PERF-DPDK-MULTICORE-PPS-F32: FAILED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
Test results for DPDK 'v19.11-rc4' and Azure image: 'SUSE SLES 15 latest':
* PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED
* VERIFY-DPDK-OVS: SKIPPED
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
* PERF-DPDK-MULTICORE-PPS-F32: PASSED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
On Wed, 2019-11-27 at 00:56 +0100, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
>
> https://git.dpdk.org/dpdk/tag/?id=v19.11-rc4
>
> 93 patches were integrated.
>
> The release notes so far:
>
> http://doc.dpdk.org/guides/rel_notes/release_19_11.html
>
> It should be completed with a list of tested hardware.
>
> This is the last release candidate for DPDK 19.11.
> After -rc4 only critical bug fixes and doc updates should be
> accepted.
>
> The major release should be done in a couple of days (Thanksgiving?).
> Please share some release validation results
> by replying to this message (at
> dev@dpdk.org
> ).
>
> If you are preparing the next release cycle, please send your v1
> patches
> before the 20.02 proposal deadline, which will happen on December
> 6th.
> It is also time to build an estimated roadmap for the next cycles.
>
> Thank you everyone
>
>
>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-11-28 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 23:56 Thomas Monjalon
2019-11-27 18:16 ` Stokes, Ian
2019-11-28 9:51 ` Luca Boccassi [this message]
2019-11-28 10:29 ` Sachin Saxena
2019-11-28 13:14 ` Xu, Qian Q
2019-11-28 12:25 ` Ali Alnubani
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=257c086cee51c1ddba6dbf907d8cabd2a2500b0e.camel@microsoft.com \
--to=luca.boccassi@microsoft.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=dev@dpdk.org \
--cc=juhlee@microsoft.com \
--cc=thomas@monjalon.net \
/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).