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, Chaoyong He <chaoyong.he@corigine.com>
Subject: |FAILURE| pw142185-142191 [PATCH] [v2,7/7] net/nfp: add trace point
Date: Mon, 08 Jul 2024 07:40:12 -0700 (PDT)	[thread overview]
Message-ID: <668bfa4c.050a0220.6ac28.3d54SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240708024543.77126-8-chaoyong.he@corigine.com>

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

_Functional Testing issues_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Monday, July 08 2024 02:45:43 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:249c34811d8f134110784872ee3f31ead1fde84c

142185-142191 --> functional testing issues

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| mtu_update      |  FAIL  |
+-----------------+--------+
| unit_tests_mbuf |  FAIL  |
+-----------------+--------+


Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown

Aggregate Results by Test Suite
+-----------------------------+--------+
|         Test Suite          | Result |
+=============================+========+
| unit_tests_mbuf             |  PASS  |
+-----------------------------+--------+
| scatter                     |  PASS  |
+-----------------------------+--------+
| vhost_virtio_user_interrupt |  PASS  |
+-----------------------------+--------+
| virtio_smoke                |  PASS  |
+-----------------------------+--------+


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  FAIL  |
+------------+--------+


Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Target: Unknown

Aggregate Results by Test Suite
+----------------------------+--------+
|         Test Suite         | Result |
+============================+========+
| crypto_perf_cryptodev_perf |  FAIL  |
+----------------------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-08 14:40 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240708024543.77126-8-chaoyong.he@corigine.com>
2024-07-08  2:27 ` |SUCCESS| pw142185-142191 [PATCH v2 7/7] net/nfp: add trace point about flow rule action qemudev
2024-07-08  2:31 ` qemudev
2024-07-08  2:47 ` |WARNING| pw142191 " checkpatch
2024-07-08 10:36 ` |PENDING| pw142185-142191 [PATCH] [v2,7/7] net/nfp: add trace point dpdklab
2024-07-08 10:47 ` dpdklab
2024-07-08 10:47 ` |FAILURE| " dpdklab
2024-07-08 10:48 ` |PENDING| " dpdklab
2024-07-08 10:48 ` dpdklab
2024-07-08 10:49 ` |FAILURE| " dpdklab
2024-07-08 10:50 ` |PENDING| " dpdklab
2024-07-08 10:51 ` dpdklab
2024-07-08 10:52 ` dpdklab
2024-07-08 10:54 ` |WARNING| " dpdklab
2024-07-08 10:54 ` |PENDING| " dpdklab
2024-07-08 10:55 ` dpdklab
2024-07-08 10:57 ` |SUCCESS| " dpdklab
2024-07-08 10:58 ` dpdklab
2024-07-08 11:15 ` |PENDING| " dpdklab
2024-07-08 11:53 ` dpdklab
2024-07-08 12:01 ` |SUCCESS| " dpdklab
2024-07-08 12:05 ` |PENDING| " dpdklab
2024-07-08 12:15 ` dpdklab
2024-07-08 12:15 ` dpdklab
2024-07-08 12:18 ` dpdklab
2024-07-08 12:20 ` dpdklab
2024-07-08 12:22 ` dpdklab
2024-07-08 12:25 ` dpdklab
2024-07-08 12:32 ` dpdklab
2024-07-08 12:36 ` |WARNING| " dpdklab
2024-07-08 12:44 ` |PENDING| " dpdklab
2024-07-08 12:46 ` dpdklab
2024-07-08 12:47 ` dpdklab
2024-07-08 12:48 ` dpdklab
2024-07-08 12:53 ` dpdklab
2024-07-08 13:02 ` |SUCCESS| " dpdklab
2024-07-08 14:30 ` |FAILURE| " dpdklab
2024-07-08 14:40 ` dpdklab [this message]
2024-07-08 14:45 ` dpdklab
2024-07-08 14:50 ` dpdklab
2024-07-08 15:00 ` |PENDING| " dpdklab
2024-07-08 15:09 ` dpdklab
2024-07-08 15:11 ` dpdklab
2024-07-08 15:13 ` dpdklab
2024-07-08 15:13 ` dpdklab
2024-07-08 15:15 ` dpdklab
2024-07-08 15:15 ` dpdklab
2024-07-08 15:26 ` dpdklab
2024-07-08 15:28 ` dpdklab
2024-07-08 15:31 ` dpdklab
2024-07-08 15:32 ` dpdklab
2024-07-08 15:34 ` dpdklab
2024-07-08 15:35 ` dpdklab
2024-07-08 15:36 ` dpdklab
2024-07-08 15:39 ` dpdklab
2024-07-08 15:40 ` dpdklab
2024-07-08 15:40 ` dpdklab
2024-07-08 15:42 ` dpdklab
2024-07-08 15:43 ` dpdklab
2024-07-08 15:44 ` dpdklab
2024-07-08 15:44 ` dpdklab
2024-07-08 15:47 ` dpdklab
2024-07-08 15:48 ` dpdklab
2024-07-08 15:52 ` dpdklab
2024-07-08 15:52 ` dpdklab
2024-07-08 15:52 ` |SUCCESS| " dpdklab
2024-07-08 15:52 ` |PENDING| " dpdklab
2024-07-08 15:53 ` dpdklab
2024-07-08 15:55 ` dpdklab
2024-07-08 15:55 ` dpdklab
2024-07-08 15:58 ` dpdklab
2024-07-08 16:01 ` dpdklab
2024-07-08 16:02 ` dpdklab
2024-07-08 16:04 ` dpdklab
2024-07-08 16:05 ` dpdklab
2024-07-08 16:06 ` dpdklab
2024-07-08 16:09 ` dpdklab
2024-07-08 16:27 ` |SUCCESS| " dpdklab
2024-07-08 16:30 ` |PENDING| " dpdklab
2024-07-09  7:34 ` |WARNING| " dpdklab
2024-07-09 16:24 ` |PENDING| " dpdklab
2024-07-09 16:38 ` |FAILURE| " dpdklab
2024-07-13 20:42 ` dpdklab
2024-07-14 10:20 ` dpdklab
2024-07-14 16:53 ` dpdklab
2024-07-15  8:43 ` 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=668bfa4c.050a0220.6ac28.3d54SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=chaoyong.he@corigine.com \
    --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).