automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Lijuan Tu <lijuan.tu@intel.com>,
	Test Report <test-report@dpdk.org>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Georgii Tkachuk <georgii.tkachuk@intel.com>,
	Qian Xu <qian.q.xu@intel.com>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw94660 [PATCH] [v4] devtools: script to track map symbols
Date: Mon, 21 Jun 2021 17:31:55 -0400 (EDT)	[thread overview]
Message-ID: <20210621213155.A202088E63@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/94660

_Functional Testing issues_

Submitter: Ray Kinsella <mdr@ashroe.eu>
Date: Monday, June 21 2021 15:35:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8050b61562723c531ad9d4736f5549050eba190e

94660 --> functional 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 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/5


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: 2/4
	Failed Tests:
		- mtu_update
		- stats_checks


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-06-21 21:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 21:31 dpdklab [this message]
2021-06-23  2:57 dpdklab
2021-06-23  5:52 dpdklab
2021-06-24  0:24 dpdklab
2021-06-24  1:31 dpdklab
2021-06-26 19:48 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=20210621213155.A202088E63@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@intel.com \
    --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).