From: Kevin Traynor <ktraynor@redhat.com>
To: Luca Boccassi <Luca.Boccassi@microsoft.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 18.11.1 patches review and test
Date: Tue, 2 Apr 2019 18:14:32 +0100 [thread overview]
Message-ID: <3641a2fe-2ed3-4c09-c0f2-ff373c520345@redhat.com> (raw)
In-Reply-To: <ddc258ce72017e38c0945341787b12931831fde8.camel@microsoft.com>
On 02/04/2019 14:21, Luca Boccassi wrote:
> Thank you, Ju!
>
+1, thanks Ju for running these and sharing. I will add summary of them
to the 18.11.1 release notes.
> Some additional information: this test was run via the LISAv2 framework
> that Microsoft uses to validate Linux and other applications on Azure.
> It can be found on Github:
>
> https://github.com/LIS/LISAv2
>
> For 18.11.1 it was just ran on Ubuntu 18.04, but for the next
> validations RHEL and SUSE will also be used.
>
nice!
> On Mon, 2019-04-01 at 23:28 +0000, Ju-Hyoung Lee wrote:
>> Tested-by @Ju-Hyoung Lee, @Luca Boccassi
>>
>>
>> [LISAv2 Test Results Summary]
>> Test Run On : 04/01/2019 10:14:22
>> ARM Image Under Test : Canonical : UbuntuServer : 18.04-LTS : latest
>> Total Test Cases : 10 (10 Passed, 0 Failed, 0 Aborted, 0
>> Skipped)
>> Total Time (dd:hh:mm) : 0:4:53
>>
>> ID TestArea
>> TestCaseName
>> TestResult TestDuration(in minutes)
>> -------------------------------------------------------------------
>> -------------------------------------------------------------------
>> -----
>> 1 DPDK VERIFY-DPDK-BUILD-AND-TESTPMD-
>> TEST
>> PASS 22.69
>> 2 DPDK VERIFY-SRIOV-FAILSAFE-FOR-
>> DPDK
>> PASS 57.81
>> DPDK-TESTPMD : Initial SRIOV : DPDK 18.11.1-rc2 : TxPPS :
>> 16959789 : RxPPS : 16849614
>> DPDK-TESTPMD : Synthetic : DPDK 18.11.1-rc2 : TxPPS : 558211
>> : RxPPS : 0
>> DPDK-TESTPMD : Re-Enable SRIOV : DPDK 18.11.1-rc2 : TxPps :
>> 12665140 : RxPps : 2493965
>> DPDK RxPPS : Difference between Initial and Re-Enabled SRIOV
>> : 16849614 : 2493965 : 85.2 %
>> 3 DPDK PERF-DPDK-SINGLE-CORE-PPS-
>> DS4 PASS
>> 15.71
>> DPDK-TEST : PASS
>> 4 DPDK PERF-DPDK-MULTICORE-PPS-
>> F32
>> PASS 27.89
>> DPDK-TEST : PASS
>> 5 DPDK VERIFY-DPDK-OVS
>> PASS 19.35
>> 6 DPDK PERF-DPDK-SINGLE-CORE-PPS-
>> DS15
>> PASS 14.78
>> DPDK-TEST : PASS
>> 7 DPDK PERF-DPDK-MULTICORE-PPS-
>> DS15
>> PASS 23.33
>> DPDK-TEST : PASS
>> 8 DPDK VERIFY-DPDK-FAILSAFE-DURING-
>> TRAFFIC
>> PASS 22.73
>> DPDK-TEST : True
>> 9 DPDK PERF-DPDK-FWD-PPS-
>> DS15
>> PASS 22.52
>> DPDK-TEST : PASS
>> 10 DPDK VERIFY-DPDK-
>> COMPLIANCE
>> PASS 7.52
>>
>>
>> Logs can be found at C:\LISAv2\QY20\TestResults\2019-01-04-10-14-16-
>> 7715
>>
>>
>> 04/01/2019 15:08:18 : [INFO ] Creating 'C:\LISAv2\QY20\Azure-QY20-
>> TestLogs.zip' from 'C:\LISAv2\QY20\TestResults\2019-01-04-10-14-16-
>> 7715'
>> 04/01/2019 15:08:19 : [INFO ] C:\LISAv2\QY20\Azure-QY20-TestLogs.zip
>> created successfully.
>> 04/01/2019 15:08:19 : [INFO ] Analyzing results..
>> 04/01/2019 15:08:19 : [INFO ] Copying all files back to original
>> working directory: C:\Jenkins-Slaves\azure-slave-2-executor-
>> 1\workspace\job-azuretest\pipeline-dpdk.
>> 04/01/2019 15:08:26 : [INFO ] Cleaning up C:\LISAv2\QY20
>> 04/01/2019 15:08:26 : [INFO ] Setting workspace back to original
>> location: C:\Jenkins-Slaves\azure-slave-2-executor-1\workspace\job-
>> azuretest\pipeline-dpdk
>> 04/01/2019 15:08:26 : [INFO ] LISAv2 exit code: 0
>>
>>
next prev parent reply other threads:[~2019-04-02 17:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 23:28 Ju-Hyoung Lee
2019-04-01 23:28 ` Ju-Hyoung Lee
2019-04-02 13:21 ` Luca Boccassi
2019-04-02 13:21 ` Luca Boccassi
2019-04-02 17:14 ` Kevin Traynor [this message]
2019-04-02 17:14 ` Kevin Traynor
-- strict thread matches above, loose matches on Subject: below --
2019-03-22 15:10 Kevin Traynor
2019-03-22 15:10 ` Kevin Traynor
2019-03-27 14:41 ` Ali Alnubani
2019-03-27 14:41 ` Ali Alnubani
2019-03-27 16:43 ` Kevin Traynor
2019-03-27 16:43 ` Kevin Traynor
2019-04-03 9:16 ` Ian Stokes
2019-04-03 9:16 ` Ian Stokes
2019-04-03 14:29 ` Kevin Traynor
2019-04-03 14:29 ` Kevin Traynor
2019-02-22 11:26 Kevin Traynor
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=3641a2fe-2ed3-4c09-c0f2-ff373c520345@redhat.com \
--to=ktraynor@redhat.com \
--cc=Luca.Boccassi@microsoft.com \
--cc=dev@dpdk.org \
--cc=juhlee@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).