From: dpdklab@iol.unh.edu
To: 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] abeef65dfdefbaedd14464dd07a8eb5f6a6ebacf
Date: Wed, 17 Jul 2019 17:59:33 -0400 (EDT) [thread overview]
Message-ID: <20190717215933.E29F2DF59F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 641 bytes --]
_Performance Testing issues_
Branch: dpdk
abeef65dfdefbaedd14464dd07a8eb5f6a6ebacf --> performance testing fail
Test environment and result as below:
Ubuntu 17.10
Kernel: 4.13.0-43-generic
GCC: gcc (Ubuntu 7.2.0-8ubuntu3) 7.2.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/1
Detail performance results:
See logs from the ci website for more information.
https://lab.dpdk.org/results/dashboard/tarballs/5452/
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-07-17 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 21:59 dpdklab [this message]
2019-07-17 22:41 dpdklab
2019-07-17 22:42 dpdklab
2019-07-17 22:44 dpdklab
2019-07-17 23:14 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=20190717215933.E29F2DF59F@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=lijuan.tu@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).