Re: [dpdk-dev] [dpdk-announce] release candidate 19.05-rc3

DPDK patches and discussions
 help / color / mirror / Atom feed

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-rc3
Date: Tue, 14 May 2019 15:26:09 +0000	[thread overview]
Message-ID: <SN6PR2101MB0992890421BFBE9B0F692149DA080@SN6PR2101MB0992.namprd21.prod.outlook.com> (raw)
In-Reply-To: <4563754.allG5gyU3x@xps>

Hello,

DPDK https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.dpdk.org%2Fdpdk%2Fsnapshot%2Fdpdk-19.05-rc3.tar.xz&amp;data=01%7C01%7Cjuhlee%40microsoft.com%7Cce65337d584e4524651b08d6d7f31501%7C72f988bf86f141af91ab2d7cd011db47%7C1&amp;sdata=MUCwy8SE3czauyFK580w70owGbumw8k9Um6HXdjpmKw%3D&amp;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&amp;data=01%7C01%7Cjuhlee%40microsoft.com%7Cce65337d584e4524651b08d6d7f31501%7C72f988bf86f141af91ab2d7cd011db47%7C1&amp;sdata=9AzibCjZpt1%2BMiYIqspncjLyS6Qa2cRAHjdVjaYnuGA%3D&amp;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&amp;data=01%7C01%7Cjuhlee%40microsoft.com%7Cce65337d584e4524651b08d6d7f31501%7C72f988bf86f141af91ab2d7cd011db47%7C1&amp;sdata=oszQ%2Fn5gmF0%2F83cfM3XUqsvqUn7U5cZd8gdJlNUJI%2F0%3D&amp;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%2F27%2F&amp;data=01%7C01%7Cjuhlee%40microsoft.com%7Cce65337d584e4524651b08d6d7f31501%7C72f988bf86f141af91ab2d7cd011db47%7C1&amp;sdata=4kbvPmS1lao8fgvjfZQMuuqdfm4VPZaup1UeDCdDeZo%3D&amp;reserved=0. 

Test results for Azure image: 'Canonical UbuntuServer 16.04-LTS 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: PASSED 
* PERF-DPDK-MULTICORE-PPS-F32: PASSED 
* VERIFY-DPDK-COMPLIANCE: ABORTED 
* VERIFY-DPDK-RING-LATENCY: PASSED 
* VERIFY-DPDK-OVS: ABORTED 
* VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC: PASSED 
* PERF-DPDK-FWD-PPS-DS15: FAILED 
* 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: PASSED 
* VERIFY-SRIOV-FAILSAFE-FOR-DPDK: PASSED 
* PERF-DPDK-SINGLE-CORE-PPS-DS15: FAILED 
* PERF-DPDK-MULTICORE-PPS-DS15: FAILED 
* 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: FAILED 
* PERF-DPDK-SINGLE-CORE-PPS-DS4: PASSED 

Test results for Azure image: 'RedHat RHEL 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: 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: FAILED 
* PERF-DPDK-SINGLE-CORE-PPS-DS4: FAILED 

Test results for Azure image: 'Openlogic CentOS 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: FAILED 

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: 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: PASSED 


Thank you,
Jenkins DPDK


-----Original Message-----
From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas Monjalon
Sent: Saturday, May 4, 2019 3:39 PM
To: announce@dpdk.org
Subject: [dpdk-announce] release candidate 19.05-rc3

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-rc3&amp;data=01%7C01%7CJuhlee%40microsoft.com%7Cabb07e17882e45ebf74d08d6d0e15fa0%7C72f988bf86f141af91ab2d7cd011db47%7C1&amp;sdata=Ync7JynRoQQxSYUMBBwHU2EPICuVubGDoYfnxClRifg%3D&amp;reserved=0

The release notes are almost complete:
	https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoc.dpdk.org%2Fguides%2Frel_notes%2Frelease_19_05.html&amp;data=01%7C01%7CJuhlee%40microsoft.com%7Cabb07e17882e45ebf74d08d6d0e15fa0%7C72f988bf86f141af91ab2d7cd011db47%7C1&amp;sdata=ewNuOmR6YodZP9eG49zpO3XPG8BpCifwKEtooF6Kxqk%3D&amp;reserved=0

Please hurry up to do the last checks and bug fixes this week, in order to have DPDK 19.05 out at the end of the week.
You may share some release validation results by replying to this message (at dev@dpdk.org).

In order to prepare the next cycle, the deprecation notices must be reviewed, and the roadmap topics proposed on the mailing list.

May the fourth be with DPDK 19.05 :-)

next prev parent reply	other threads:[~2019-05-14 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-04 22:39 Thomas Monjalon
2019-05-04 22:39 ` Thomas Monjalon
2019-05-14 15:26 ` Ju-Hyoung Lee [this message]
2019-05-14 15:26   ` 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=SN6PR2101MB0992890421BFBE9B0F692149DA080@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).