From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw72446 [PATCH] app/flow-perf: fix condition of hairpin queues setup
Date: Tue, 30 Jun 2020 10:40:32 -0400 (EDT) [thread overview]
Message-ID: <20200630144032.5614D6D437@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Test-Label: iol-broadcom-Performance
Test-Status: FAILURE
http://dpdk.org/patch/72446
_Performance Testing issues_
Submitter: Wisam Monther <wisamm@mellanox.com>
Date: Tuesday, June 30 2020 08:10:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:014a7ec6c418eaf24a13be8ade8229638ddc6eed
72446 --> performance testing fail
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 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.
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/11734/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-06-30 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 14:40 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-30 17:47 dpdklab
2020-06-30 15:06 dpdklab
2020-06-30 8:33 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=20200630144032.5614D6D437@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.com \
--cc=dpdk-test-reports@iol.unh.edu \
--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).