automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Test Report <test-report@dpdk.org>,
	Georgii Tkachuk <georgii.tkachuk@intel.com>,
	Qian Xu <qian.q.xu@intel.com>, Lijuan Tu <lijuan.tu@intel.com>
Cc: dpdk-test-reports@iol.unh.edu, Suanming Mou <suanmingm@nvidia.com>
Subject: |FAILURE| pw137673 [PATCH] crypto/mlx5: add virtual function device
Date: Fri, 01 Mar 2024 11:22:05 -0800 (PST)	[thread overview]
Message-ID: <65e22add.c80a0220.d5465.6d14SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301123037.1216332-1-suanmingm@nvidia.com>

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

_Functional Testing issues_

Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Friday, March 01 2024 12:30:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5ac50824383c2683c0dfdf24c6dc493f1fa54852

137673 --> functional testing fail

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/2
	Failed Tests:
		- mtu_update


Ubuntu 20.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/3


Ubuntu 20.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/3


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-01 19:22 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301123037.1216332-1-suanmingm@nvidia.com>
2024-03-01 12:32 ` |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device ID checkpatch
2024-03-01 13:11 ` |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device dpdklab
2024-03-01 13:12 ` |FAILURE| " dpdklab
2024-03-01 13:13 ` |SUCCESS| " dpdklab
2024-03-01 13:13 ` dpdklab
2024-03-01 13:13 ` dpdklab
2024-03-01 13:13 ` dpdklab
2024-03-01 13:14 ` dpdklab
2024-03-01 13:14 ` dpdklab
2024-03-01 13:15 ` dpdklab
2024-03-01 13:15 ` dpdklab
2024-03-01 13:15 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:16 ` dpdklab
2024-03-01 13:18 ` dpdklab
2024-03-01 13:24 ` dpdklab
2024-03-01 13:24 ` |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device ID 0-day Robot
2024-03-01 13:25 ` |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device dpdklab
2024-03-01 13:27 ` dpdklab
2024-03-01 13:28 ` |FAILURE| " dpdklab
2024-03-01 13:29 ` |SUCCESS| " dpdklab
2024-03-01 13:31 ` dpdklab
2024-03-01 13:31 ` dpdklab
2024-03-01 13:31 ` dpdklab
2024-03-01 13:31 ` dpdklab
2024-03-01 13:32 ` dpdklab
2024-03-01 13:32 ` dpdklab
2024-03-01 13:33 ` dpdklab
2024-03-01 13:33 ` |FAILURE| " dpdklab
2024-03-01 13:33 ` |SUCCESS| " dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:34 ` dpdklab
2024-03-01 13:35 ` dpdklab
2024-03-01 13:35 ` dpdklab
2024-03-01 13:35 ` dpdklab
2024-03-01 13:36 ` dpdklab
2024-03-01 13:36 ` dpdklab
2024-03-01 13:36 ` dpdklab
2024-03-01 13:36 ` dpdklab
2024-03-01 13:37 ` dpdklab
2024-03-01 13:40 ` dpdklab
2024-03-01 13:40 ` dpdklab
2024-03-01 13:40 ` dpdklab
2024-03-01 13:41 ` dpdklab
2024-03-01 13:41 ` dpdklab
2024-03-01 13:41 ` dpdklab
2024-03-01 13:41 ` dpdklab
2024-03-01 13:41 ` dpdklab
2024-03-01 13:42 ` dpdklab
2024-03-01 13:46 ` dpdklab
2024-03-01 14:14 ` dpdklab
2024-03-01 14:16 ` dpdklab
2024-03-01 17:07 ` dpdklab
2024-03-01 17:56 ` dpdklab
2024-03-01 17:57 ` dpdklab
2024-03-01 18:05 ` |FAILURE| " dpdklab
2024-03-01 18:06 ` |SUCCESS| " dpdklab
2024-03-01 19:22 ` dpdklab [this message]
2024-03-01 19:44 ` dpdklab
2024-03-02  3:00 ` dpdklab
2024-03-02  3:07 ` dpdklab
2024-03-02  6:10 ` |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device ID qemudev
2024-03-02  6:14 ` qemudev
2024-03-02 17:24 ` |SUCCESS| pw137673 [PATCH] crypto/mlx5: add virtual function device dpdklab
2024-03-02 19:48 ` dpdklab
2024-03-02 19:55 ` dpdklab
2024-03-05  1:08 ` dpdklab
2024-03-05  1:41 ` dpdklab
2024-03-05  2:13 ` 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=65e22add.c80a0220.d5465.6d14SMTPIN_ADDED_MISSING@mx.google.com \
    --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=suanmingm@nvidia.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).