From: Kevin Traynor <ktraynor@redhat.com>
To: Lili Deng <Lili.Deng@microsoft.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Ali Alnubani <alialnu@mellanox.com>,
benjamin walker <benjamin.walker@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Ian Stokes <ian.stokes@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Luca Boccassi <bluca@debian.org>, pingx yu <pingx.yu@intel.com>,
qian q xu <qian.q.xu@intel.com>,
Raslan Darawsheh <rasland@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
yuan peng <yuan.peng@intel.com>,
zhaoyan chen <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-dev] 18.11.6 (LTS) patches review and test
Date: Thu, 9 Jan 2020 14:03:24 +0000 [thread overview]
Message-ID: <16876742-f7dd-d7c0-f43a-4547a0280993@redhat.com> (raw)
In-Reply-To: <HK0P153MB0290E5EC547B223C3071FFC9E7270@HK0P153MB0290.APCP153.PROD.OUTLOOK.COM>
On 30/12/2019 08:56, Lili Deng wrote:
> Hi Kevin,
>
>
>
> I'd like to sign off validation dpdk-stable-18.11.6-rc1 against Azure gallery images.
>
> Version used - https://git.dpdk.org/dpdk-stable/snapshot/dpdk-stable-18.11.6-rc1.tar.xz<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.dpdk.org%2Fdpdk-stable%2Fsnapshot%2Fdpdk-stable-18.11.6-rc1.tar.xz&data=02%7C01%7CLili.Deng%40microsoft.com%7C2f2d046d52444b0b36e408d78cf5cc47%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637132859661424426&sdata=q2ZOJFlR0fZgpfU5FnVp%2FoTeYu8qubAWD9Nolw4kuEo%3D&reserved=0>
>
>
>
> Below are test matrix and results -
>
> Tests
>
> Ubuntu 16.04
>
> Ubuntu 18.04
>
> Ubuntu 19.10
>
> RHEL 7-RAW
>
> SLES 15
>
> RHEL 7.5
>
> CentOS 7.5
>
> RHEL 8
>
> CentOS 8
>
> VERIFY-DPDK-FAILSAFE-DURING-TRAFFIC
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> VERIFY-DPDK-BUILD-AND-TESTPMD-TEST
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> VERIFY-SRIOV-FAILSAFE-FOR-DPDK
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> VERIFY-DPDK-COMPLIANCE
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> VERIFY-DPDK-OVS
>
> PASS
>
> PASS
>
> PASS
>
> SKIPPED
>
> SKIPPED
>
> SKIPPED
>
> SKIPPED
>
> SKIPPED
>
> SKIPPED
>
> VERIFY-DPDK-RING-LATENCY
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PERF-DPDK-FWD-PPS-DS15
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PERF-DPDK-SINGLE-CORE-PPS-DS4
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PERF-DPDK-SINGLE-CORE-PPS-DS15
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PERF-DPDK-MULTICORE-PPS-DS15
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PASS
>
> PERF-DPDK-MULTICORE-PPS-F32
>
> PASS
>
> PASS
>
> PASS
>
> FAIL
>
> PASS
>
> PASS
>
> FAIL
>
> PASS
>
> FAIL
>
>
>
> FAIL reason for PERF-DPDK-MULTICORE-PPS-F32 - the performance is not expected in some rate.
>
> For example, when run 3 times, only 1/3 pass, maybe the size Standard_F32s_v2 on Azure is unstable.
>
>
Thanks Lili. I think this is ok. It seems this test has been reporting
fails in previous testing cycles too. Perhaps in future the thresholds
could be changed so it will check if there are regressions?
fyi - if you want to be added to the list of validation contacts for
dpdk stable
(https://git.dpdk.org/tools/stable-scripts/tree/validation-contacts),
let me know. Not a requirement, just to make it easier for being
notified about an RC's etc.
Kevin.
>
> Thanks,
>
> Lili
>
<snip>
next prev parent reply other threads:[~2020-01-09 14:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 11:42 Kevin Traynor
2019-12-24 10:07 ` Yu, PingX
2020-01-08 18:32 ` Kevin Traynor
2020-01-08 18:34 ` Kevin Traynor
2020-01-09 8:30 ` Julien Meunier
2020-01-09 14:18 ` Kevin Traynor
2020-01-09 17:10 ` Trahe, Fiona
2019-12-25 5:17 ` Pei Zhang
[not found] ` <BN8PR21MB1217C1C2EF180C4D29DAF216DA280@BN8PR21MB1217.namprd21.prod.outlook.com>
[not found] ` <HK0P153MB0290B7D0487D922C3854BAF7E7270@HK0P153MB0290.APCP153.PROD.OUTLOOK.COM>
[not found] ` <MN2PR21MB123271BB60DB0E70ACD2FA91DA270@MN2PR21MB1232.namprd21.prod.outlook.com>
[not found] ` <HK0P153MB0290EECF6665FA00EC22867BE7270@HK0P153MB0290.APCP153.PROD.OUTLOOK.COM>
[not found] ` <MN2PR21MB123240BDE6BA187B4DE15F55DA270@MN2PR21MB1232.namprd21.prod.outlook.com>
2019-12-30 8:56 ` Lili Deng
2020-01-09 14:03 ` Kevin Traynor [this message]
2020-01-09 17:32 ` [dpdk-dev] [EXTERNAL] " Ju-Hyoung Lee
2020-01-09 13:38 ` [dpdk-dev] " Kevin Traynor
2019-12-26 13:35 ` Ali Alnubani
2020-01-09 13:41 ` Kevin Traynor
2020-01-14 14:40 ` Kevin Traynor
2020-01-19 5:31 ` Yu, PingX
2020-01-19 21:05 ` Kevin Traynor
2020-01-30 14:58 ` Stokes, Ian
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=16876742-f7dd-d7c0-f43a-4547a0280993@redhat.com \
--to=ktraynor@redhat.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=Lili.Deng@microsoft.com \
--cc=akhil.goyal@nxp.com \
--cc=alialnu@mellanox.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@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).