automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141921 [PATCH] [v3] config/arm: add Ampere AmpereOneX pl
Date: Thu, 27 Jun 2024 11:36:11 -0700 (PDT)	[thread overview]
Message-ID: <667db11b.050a0220.19801.0517SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240627024414.8598-1-jiangyutang@os.amperecomputing.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/141921

_Functional Testing PASS_

Submitter: Yutang Jiang <jiangyutang@os.amperecomputing.com>
Date: Thursday, June 27 2024 02:44:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c15902587b538ff02cfb0fbb4dd481f1503d936b

141921 --> functional testing pass

Test environment and result as below:

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 |
+=============================+========+
| scatter                     |  PASS  |
+-----------------------------+--------+
| unit_tests_mbuf             |  PASS  |
+-----------------------------+--------+
| vhost_virtio_user_interrupt |  PASS  |
+-----------------------------+--------+
| virtio_smoke                |  PASS  |
+-----------------------------+--------+


Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: Unknown

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-27 18:36 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240627024414.8598-1-jiangyutang@os.amperecomputing.com>
2024-06-27  6:55 ` |SUCCESS| pw141921 [PATCH v3] config/arm: add Ampere AmpereOneX platform qemudev
2024-06-27  6:59 ` qemudev
2024-06-27  7:23 ` |WARNING| " checkpatch
2024-06-27 18:14 ` |SUCCESS| pw141921 [PATCH] [v3] config/arm: add Ampere AmpereOneX pl dpdklab
2024-06-27 18:23 ` dpdklab
2024-06-27 18:36 ` dpdklab [this message]
2024-06-27 20:43 ` dpdklab
2024-06-27 20:47 ` dpdklab
2024-06-27 20:55 ` dpdklab
2024-06-27 21:09 ` dpdklab
2024-06-27 22:08 ` dpdklab
2024-06-27 22:09 ` dpdklab
2024-06-27 22:12 ` dpdklab
2024-06-27 22:14 ` dpdklab
2024-06-27 22:17 ` dpdklab
2024-06-27 22:18 ` dpdklab
2024-06-27 22:20 ` dpdklab
2024-06-27 22:24 ` dpdklab
2024-06-27 22:48 ` |PENDING| " dpdklab
2024-06-27 22:57 ` |SUCCESS| " dpdklab
2024-06-27 23:08 ` |PENDING| " dpdklab
2024-06-27 23:13 ` dpdklab
2024-06-27 23:16 ` dpdklab
2024-06-27 23:20 ` dpdklab
2024-06-27 23:22 ` dpdklab
2024-06-27 23:23 ` dpdklab
2024-06-27 23:28 ` dpdklab
2024-06-27 23:31 ` dpdklab
2024-06-27 23:34 ` dpdklab
2024-06-27 23:35 ` dpdklab
2024-06-27 23:35 ` dpdklab
2024-06-27 23:35 ` dpdklab
2024-06-27 23:40 ` dpdklab
2024-06-27 23:42 ` dpdklab
2024-06-27 23:46 ` |SUCCESS| " dpdklab
2024-06-27 23:50 ` dpdklab
2024-06-28  0:00 ` dpdklab
2024-06-28  0:08 ` dpdklab
2024-06-28  0:43 ` dpdklab
2024-06-28  2:37 ` dpdklab
2024-06-28  2:42 ` dpdklab
2024-06-28  2:46 ` dpdklab
2024-06-28  2:51 ` dpdklab
2024-06-28  3:00 ` dpdklab
2024-06-28  3:02 ` dpdklab
2024-06-28  3:04 ` dpdklab
2024-06-28  3:10 ` dpdklab
2024-06-28  3:11 ` dpdklab
2024-06-28  3:11 ` dpdklab
2024-06-28  3:12 ` dpdklab
2024-06-28  3:13 ` dpdklab
2024-06-28  3:13 ` dpdklab
2024-06-28  3:14 ` dpdklab
2024-06-28  3:14 ` dpdklab
2024-06-28  3:15 ` dpdklab
2024-06-28  3:16 ` dpdklab
2024-06-28  3:17 ` dpdklab
2024-06-28  3:20 ` dpdklab
2024-06-28  3:22 ` dpdklab
2024-06-28  3:23 ` dpdklab
2024-06-28  3:24 ` dpdklab
2024-06-28  3:25 ` dpdklab
2024-06-28  3:30 ` dpdklab
2024-06-28  3:30 ` dpdklab
2024-06-28  3:35 ` dpdklab
2024-06-28  3:36 ` dpdklab
2024-06-28  3:36 ` dpdklab
2024-06-28  3:38 ` dpdklab
2024-06-28  3:39 ` dpdklab
2024-06-28  3:40 ` dpdklab
2024-06-28  3:43 ` dpdklab
2024-06-28  3:44 ` dpdklab
2024-06-28  3:44 ` dpdklab
2024-06-28  3:47 ` dpdklab
2024-06-28  3:48 ` dpdklab
2024-06-28  3:49 ` dpdklab
2024-06-28  3:52 ` dpdklab
2024-06-28  3:53 ` dpdklab
2024-06-28  3:53 ` dpdklab
2024-06-28  3:56 ` dpdklab
2024-06-28  4:00 ` dpdklab
2024-06-28  4:02 ` dpdklab
2024-06-28  4:07 ` dpdklab
2024-06-28  4:09 ` dpdklab
2024-06-28  4:16 ` dpdklab
2024-06-28  4:28 ` dpdklab
2024-06-28  4:35 ` dpdklab
2024-06-28  4:39 ` dpdklab
2024-06-28  4:42 ` dpdklab
2024-06-28  5:32 ` dpdklab
2024-06-28  5:42 ` dpdklab
2024-06-28  5:53 ` dpdklab
2024-06-28  6:01 ` dpdklab
2024-06-28  6:03 ` dpdklab
2024-06-28  6:03 ` dpdklab
2024-06-28  6:08 ` dpdklab
2024-06-28  6:10 ` dpdklab
2024-06-28  6:17 ` dpdklab
2024-06-28  6:32 ` dpdklab
2024-06-28  6:35 ` dpdklab
2024-06-28  6:38 ` dpdklab
2024-06-28  6:38 ` dpdklab
2024-06-28  6:46 ` dpdklab
2024-06-28  6:54 ` dpdklab
2024-06-28  6:55 ` dpdklab
2024-06-28  7:02 ` dpdklab
2024-06-28  7:03 ` dpdklab
2024-06-28  7:03 ` dpdklab
2024-06-28 15:17 ` dpdklab
2024-06-28 15:47 ` dpdklab
2024-06-29  4:21 ` 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=667db11b.050a0220.19801.0517SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).