From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@mellanox.com>,
Erez Scop <erezsc@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw62809 [PATCH] net/mlx5: fix compiling without definition
Date: Tue, 12 Nov 2019 13:18:55 -0500 (EST) [thread overview]
Message-ID: <20191112181855.1D94D6D4DE@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
Test-Label: iol-mellanox-Performance
Test-Status: FAILURE
http://dpdk.org/patch/62809
_Performance Testing issues_
Submitter: Bing Zhao <bingz@mellanox.com>
Date: Sunday, November 10 2019 16:37:21
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: master
CommitID:ba465d0cf8672032e0339cda7ef3a083b2d8a2af
62809 --> performance testing fail
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-generic
GCC: 7.4
NIC: Mellanox ConnectX-5 100000 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/patchsets/8458/
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-11-12 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 18:18 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-13 22:34 dpdklab
2019-11-13 20:16 dpdklab
2019-11-10 17:26 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=20191112181855.1D94D6D4DE@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@mellanox.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=erezsc@mellanox.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).