automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Erez Scop <erezsc@mellanox.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Ali Alnubani <alialnu@mellanox.com>,
	Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw66895-66920 [PATCH] [v1, 01/26] graph: define the public API for graph support
Date: Wed, 18 Mar 2020 20:19:32 -0400 (EDT)	[thread overview]
Message-ID: <20200319001932.024556D54D@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2416 bytes --]

Test-Label: iol-mellanox-Performance
Test-Status: FAILURE
http://dpdk.org/patch/66895

_Performance Testing issues_

Submitter: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Date: Wednesday, March 18 2020 21:35:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:716f9bb42ecb6df640d4dffebe1ec55aaab29ba0

66895-66920 --> performance testing fail

Test environment and result as below:

Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 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
Compiler: 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.

Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6

Detail performance results: 
+------------+---------+-------------------------------------+
| frame_size | txd/rxd | throughput difference from expected |
+============+=========+=====================================+
| 64         | 256     | -0.488                              |
+------------+---------+-------------------------------------+
| 128        | 256     | 0.049                               |
+------------+---------+-------------------------------------+
| 256        | 256     | -0.117                              |
+------------+---------+-------------------------------------+
| 512        | 256     | 0.016                               |
+------------+---------+-------------------------------------+
| 1024       | 256     | 0.004                               |
+------------+---------+-------------------------------------+
| 1518       | 256     | 0.006                               |
+------------+---------+-------------------------------------+

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/10037/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2020-03-19  0:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19  0:19 dpdklab [this message]
2020-03-19  0:59 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=20200319001932.024556D54D@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).