From: Ju-Hyoung Lee <juhlee@microsoft.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Luca Boccassi <Luca.Boccassi@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
"Adrian Vladu (Cloudbase Solutions SRL)" <v-advlad@microsoft.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 19.05-rc4
Date: Tue, 14 May 2019 15:30:38 +0000 [thread overview]
Message-ID: <SN6PR2101MB0992959DDB498E18EE3D252CDA080@SN6PR2101MB0992.namprd21.prod.outlook.com> (raw)
Message-ID: <20190514153038.6LiWBCpAJprjwm74Pzk4Rd7xyxdU7-NRtRvOATPKKLU@z> (raw)
In-Reply-To: <3010866.ptfx1ugjOl@xps>
Hello,
DPDK https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.dpdk.org%2Fdpdk%2Fsnapshot%2Fdpdk-19.05-rc4.tar.xz&data=01%7C01%7Cjuhlee%40microsoft.com%7C9a54854a243946e49c0e08d6d7f8e325%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=Ako1OMrLmgmRTpExbu9bXSIaC4DqciA%2B7QOqw3%2BomFQ%3D&reserved=0 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLIS%2FLISAv2&data=01%7C01%7Cjuhlee%40microsoft.com%7C9a54854a243946e49c0e08d6d7f8e325%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=lggxTezw1qSITAmYsLcvZXx6w6%2BZiPZ1YwsWa9Y%2F4dk%3D&reserved=0).
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-DPDK-OVS - builds OVS with DPDK support and tests if the OVS DPDK ports can be created (only on Ubuntu)
* 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fshemminger%2Fdpdk-ring-ping.git&data=01%7C01%7Cjuhlee%40microsoft.com%7C9a54854a243946e49c0e08d6d7f8e325%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=a2KnjAa8yTkunXYZ8I8J3JbXnFKvyDqXgKtxGNEzUu4%3D&reserved=0
DPDK job exited with status: UNSTABLE - https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinuxpipeline.westus2.cloudapp.azure.com%2Fjob%2Fpipeline-dpdk-validation%2Fjob%2Fmaster%2F28%2F&data=01%7C01%7Cjuhlee%40microsoft.com%7C9a54854a243946e49c0e08d6d7f8e325%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=kQB1zE5kar25f46kRzV9ruzuvHR2WHZwLAmA%2BAaoA%2FA%3D&reserved=0.
Test results for Azure image: 'Canonical UbuntuServer 16.04-LTS latest':
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
* PERF-DPDK-SINGLE-CORE-PPS-DS15: PASSED
* PERF-DPDK-MULTICORE-PPS-DS15: FAILED
* PERF-DPDK-MULTICORE-PPS-F32: PASSED
* VERIFY-DPDK-COMPLIANCE: PASSED
* VERIFY-DPDK-RING-LATENCY: PASSED
* VERIFY-DPDK-OVS: ABORTED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
* PERF-DPDK-FWD-PPS-DS15: PASSED
* PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED
Test results for Azure image: 'Canonical UbuntuServer 18.04-DAILY-LTS latest':
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
* PERF-DPDK-SINGLE-CORE-PPS-DS15: PASSED
* PERF-DPDK-MULTICORE-PPS-DS15: PASSED
* PERF-DPDK-MULTICORE-PPS-F32: PASSED
* VERIFY-DPDK-COMPLIANCE: PASSED
* VERIFY-DPDK-RING-LATENCY: PASSED
* VERIFY-DPDK-OVS: ABORTED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
* PERF-DPDK-FWD-PPS-DS15: PASSED
* PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
Test results for Azure image: 'RedHat RHEL 7-RAW latest':
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: FAILED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: FAILED
* PERF-DPDK-SINGLE-CORE-PPS-DS15: FAILED
* PERF-DPDK-MULTICORE-PPS-DS15: PASSED
* PERF-DPDK-MULTICORE-PPS-F32: PASSED
* VERIFY-DPDK-COMPLIANCE: PASSED
* VERIFY-DPDK-RING-LATENCY: PASSED
* VERIFY-DPDK-OVS: FAILED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
* PERF-DPDK-FWD-PPS-DS15: PASSED
* PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED
Test results for Azure image: 'RedHat RHEL 7.5 latest':
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
* PERF-DPDK-SINGLE-CORE-PPS-DS15: PASSED
* PERF-DPDK-MULTICORE-PPS-DS15: PASSED
* PERF-DPDK-MULTICORE-PPS-F32: PASSED
* VERIFY-DPDK-COMPLIANCE: PASSED
* VERIFY-DPDK-RING-LATENCY: PASSED
* VERIFY-DPDK-OVS: PASSED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
* PERF-DPDK-FWD-PPS-DS15: PASSED
* PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
Test results for Azure image: 'Openlogic CentOS 7.5 latest':
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: FAILED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
* PERF-DPDK-SINGLE-CORE-PPS-DS15: PASSED
* PERF-DPDK-MULTICORE-PPS-DS15: FAILED
* PERF-DPDK-MULTICORE-PPS-F32: FAILED
* VERIFY-DPDK-COMPLIANCE: PASSED
* VERIFY-DPDK-RING-LATENCY: PASSED
* VERIFY-DPDK-OVS: FAILED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: FAILED
* PERF-DPDK-FWD-PPS-DS15: PASSED
* PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
Test results for Azure image: 'SUSE SLES 15 latest':
* VERIFY-DPDK-BUILD-AND-TESTPMD-TEST: PASSED
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED
* PERF-DPDK-SINGLE-CORE-PPS-DS15: PASSED
* PERF-DPDK-MULTICORE-PPS-DS15: PASSED
* PERF-DPDK-MULTICORE-PPS-F32: PASSED
* VERIFY-DPDK-COMPLIANCE: PASSED
* VERIFY-DPDK-RING-LATENCY: PASSED
* VERIFY-DPDK-OVS: PASSED
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED
* PERF-DPDK-FWD-PPS-DS15: PASSED
* PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED
Thank you,
Jenkins DPDK
-----Original Message-----
From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas Monjalon
Sent: Thursday, May 9, 2019 4:35 PM
To: announce@dpdk.org
Subject: [dpdk-announce] release candidate 19.05-rc4
A new DPDK release candidate is ready for testing:
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.dpdk.org%2Fdpdk%2Ftag%2F%3Fid%3Dv19.05-rc4&data=01%7C01%7CJuhlee%40microsoft.com%7C8ccb956a220e4e39f82008d6d4d70157%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=LIRrm4x5kUUWz2Zku3ywK1AaVI2ivqJU4bvB8LfaZKs%3D&reserved=0
The release notes:
https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.dpdk.org%2Fguides%2Frel_notes%2Frelease_19_05.html&data=01%7C01%7CJuhlee%40microsoft.com%7C8ccb956a220e4e39f82008d6d4d70157%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=jdBPSV5pxpUKBj3UUZgi8DnWwDmnJq%2FLA1%2BmStSsV4A%3D&reserved=0
41 patches (docs and fixes) were integrated.
This is the last release candidate for DPDK 19.05.
You may share some release validation results by replying to this message (at dev@dpdk.org).
If no objection, the version 19.05.0 will be out on May 13.
The deprecation notices for 19.08 may still be reviewed during the last days of this release cycle.
If you are preparing the next release cycle, please send your v1 patches before the 19.08 proposal deadline, which will happen on June 3.
It is also time to build an estimated roadmap for the next cycles.
PS: The CfP for Europe conference of September is closing at the end of May
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.dpdk.org%2Fevent%2Fdpdk-userspace-bordeaux%2F&data=01%7C01%7CJuhlee%40microsoft.com%7C8ccb956a220e4e39f82008d6d4d70157%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=aUrwke7xEz9m13qj%2Bjj4PZbhjs3COZYEOY%2FjILwI8OI%3D&reserved=0
next prev parent reply other threads:[~2019-05-14 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 23:35 Thomas Monjalon
2019-05-09 23:35 ` Thomas Monjalon
2019-05-11 17:46 ` dwilder
2019-05-11 17:46 ` dwilder
2019-05-13 12:10 ` Raslan Darawsheh
2019-05-13 12:10 ` Raslan Darawsheh
2019-05-14 15:30 ` Ju-Hyoung Lee [this message]
2019-05-14 15:30 ` Ju-Hyoung Lee
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=SN6PR2101MB0992959DDB498E18EE3D252CDA080@SN6PR2101MB0992.namprd21.prod.outlook.com \
--to=juhlee@microsoft.com \
--cc=Luca.Boccassi@microsoft.com \
--cc=dev@dpdk.org \
--cc=sthemmin@microsoft.com \
--cc=thomas@monjalon.net \
--cc=v-advlad@microsoft.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).