automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw66653-66654 [PATCH] [v2, 1/2] common/qat: get version of QAT firmware
Date: Fri, 13 Mar 2020 16:16:33 -0400 (EDT)	[thread overview]
Message-ID: <20200313201633.F3A716D4D4@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-intel-Performance
Test-Status: FAILURE
http://dpdk.org/patch/66653

_Performance Testing issues_

Submitter: Adam Dybkowski <adamx.dybkowski@intel.com>
Date: Friday, March 13 2020 15:24:22 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2a860943b847fbd44e08ef4f1ca66de759875c9e

66653-66654 --> performance testing fail

Test environment and result as below:

Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: 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.

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

UNH-IOL DPDK Community Lab

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

                 reply	other threads:[~2020-03-13 20:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200313201633.F3A716D4D4@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).