From: dpdklab@iol.unh.edu
To: Georgii Tkachuk <georgii.tkachuk@intel.com>,
Qian Xu <qian.q.xu@intel.com>, Lijuan Tu <lijuan.tu@intel.com>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| [GIT MASTER] d0185e7a58fd2e3dfe1ab66accdee14e3cd72ea7
Date: Fri, 13 Sep 2019 14:19:53 -0400 (EDT) [thread overview]
Message-ID: <20190913181953.3AA036D557@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
_Performance Testing issues_
Branch: dpdk-next-net
d0185e7a58fd2e3dfe1ab66accdee14e3cd72ea7 --> performance testing fail
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-generic
GCC: 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/0
Detail performance results:
There were no deltas reported. There may have been an issue with the test harness. If logs are available, download them from the ci website for more information.
Ubuntu 18.04
Kernel: 4.15.0-generic
GCC: 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/0
Detail performance results:
There were no deltas reported. There may have been an issue with the test harness. If logs are available, download them from the ci website for more information.
https://lab.dpdk.org/results/dashboard/tarballs/6148/
UNH-IOL DPDK Performance Test Lab
To manage your email subscriptions visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2019-09-13 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 18:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-13 18:25 dpdklab
2019-09-13 18:21 dpdklab
2019-09-13 18:19 dpdklab
2019-09-13 18:19 dpdklab
2019-09-13 18:17 dpdklab
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=20190913181953.3AA036D557@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=georgii.tkachuk@intel.com \
--cc=lijuan.tu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=test-report@dpdk.org \
/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).