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| pw142506-142509 [PATCH] [v2,4/4] doc: fix typo in l2fwd-cr
Date: Thu, 18 Jul 2024 09:59:24 -0700 (PDT)	[thread overview]
Message-ID: <669949ec.050a0220.c87f8.4dd4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240717154908.2281023-5-joel.kavanagh@intel.com>

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142509

_Functional Testing PASS_

Submitter: Joel Kavanagh <joel.kavanagh@intel.com>
Date: Wednesday, July 17 2024 15:49:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142506-142509 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#168866

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps

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


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps

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


Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps

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


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

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-18 16:59 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240717154908.2281023-5-joel.kavanagh@intel.com>
2024-07-18 13:29 ` |SUCCESS| pw142506-142509 [PATCH v2 4/4] doc: fix typo in l2fwd-crypto guide qemudev
2024-07-18 13:33 ` qemudev
2024-07-18 13:51 ` |SUCCESS| pw142509 " checkpatch
2024-07-18 15:26 ` |PENDING| pw142506-142509 [PATCH] [v2,4/4] doc: fix typo in l2fwd-cr dpdklab
2024-07-18 15:33 ` dpdklab
2024-07-18 15:39 ` |SUCCESS| " dpdklab
2024-07-18 15:46 ` dpdklab
2024-07-18 15:48 ` dpdklab
2024-07-18 15:55 ` |PENDING| " dpdklab
2024-07-18 15:56 ` |SUCCESS| " dpdklab
2024-07-18 15:56 ` dpdklab
2024-07-18 15:58 ` |PENDING| " dpdklab
2024-07-18 16:01 ` dpdklab
2024-07-18 16:02 ` dpdklab
2024-07-18 16:03 ` |SUCCESS| " dpdklab
2024-07-18 16:03 ` |PENDING| " dpdklab
2024-07-18 16:04 ` dpdklab
2024-07-18 16:07 ` |SUCCESS| " dpdklab
2024-07-18 16:08 ` |PENDING| " dpdklab
2024-07-18 16:09 ` |SUCCESS| " dpdklab
2024-07-18 16:09 ` dpdklab
2024-07-18 16:10 ` dpdklab
2024-07-18 16:10 ` |PENDING| " dpdklab
2024-07-18 16:11 ` dpdklab
2024-07-18 16:12 ` dpdklab
2024-07-18 16:13 ` |SUCCESS| " dpdklab
2024-07-18 16:16 ` dpdklab
2024-07-18 16:19 ` |PENDING| " dpdklab
2024-07-18 16:21 ` dpdklab
2024-07-18 16:22 ` dpdklab
2024-07-18 16:22 ` dpdklab
2024-07-18 16:25 ` dpdklab
2024-07-18 16:25 ` dpdklab
2024-07-18 16:26 ` |SUCCESS| " dpdklab
2024-07-18 16:27 ` |PENDING| " dpdklab
2024-07-18 16:30 ` dpdklab
2024-07-18 16:31 ` dpdklab
2024-07-18 16:32 ` dpdklab
2024-07-18 16:37 ` dpdklab
2024-07-18 16:40 ` dpdklab
2024-07-18 16:41 ` dpdklab
2024-07-18 16:42 ` dpdklab
2024-07-18 16:42 ` dpdklab
2024-07-18 16:44 ` dpdklab
2024-07-18 16:45 ` dpdklab
2024-07-18 16:48 ` dpdklab
2024-07-18 16:50 ` |SUCCESS| " dpdklab
2024-07-18 16:51 ` dpdklab
2024-07-18 16:51 ` |PENDING| " dpdklab
2024-07-18 16:54 ` dpdklab
2024-07-18 16:55 ` |SUCCESS| " dpdklab
2024-07-18 16:55 ` |PENDING| " dpdklab
2024-07-18 16:57 ` dpdklab
2024-07-18 16:59 ` dpdklab [this message]
2024-07-18 16:59 ` dpdklab
2024-07-18 17:00 ` dpdklab
2024-07-18 17:01 ` dpdklab
2024-07-18 17:02 ` dpdklab
2024-07-18 17:03 ` dpdklab
2024-07-18 17:04 ` dpdklab
2024-07-18 17:05 ` dpdklab
2024-07-18 17:06 ` dpdklab
2024-07-18 17:08 ` dpdklab
2024-07-18 17:09 ` dpdklab
2024-07-18 17:10 ` dpdklab
2024-07-18 17:11 ` dpdklab
2024-07-18 17:16 ` dpdklab
2024-07-18 17:17 ` |SUCCESS| " dpdklab
2024-07-18 17:17 ` |PENDING| " dpdklab
2024-07-18 17:17 ` dpdklab
2024-07-18 17:18 ` dpdklab
2024-07-18 17:21 ` dpdklab
2024-07-18 17:22 ` dpdklab
2024-07-18 17:24 ` dpdklab
2024-07-18 17:24 ` dpdklab
2024-07-18 17:25 ` dpdklab
2024-07-18 17:30 ` dpdklab
2024-07-18 17:32 ` dpdklab
2024-07-18 17:32 ` dpdklab
2024-07-18 17:32 ` dpdklab
2024-07-18 17:34 ` dpdklab
2024-07-18 17:34 ` dpdklab
2024-07-18 17:34 ` dpdklab
2024-07-18 17:35 ` dpdklab
2024-07-18 17:37 ` dpdklab
2024-07-18 17:38 ` dpdklab
2024-07-18 17:38 ` dpdklab
2024-07-18 17:39 ` dpdklab
2024-07-18 17:39 ` dpdklab
2024-07-18 17:39 ` dpdklab
2024-07-18 17:40 ` dpdklab
2024-07-18 17:41 ` dpdklab
2024-07-18 17:41 ` |SUCCESS| " dpdklab
2024-07-18 17:41 ` |PENDING| " dpdklab
2024-07-18 17:41 ` dpdklab
2024-07-18 17:42 ` dpdklab
2024-07-18 17:43 ` dpdklab
2024-07-18 17:43 ` dpdklab
2024-07-18 17:45 ` dpdklab
2024-07-18 17:45 ` dpdklab
2024-07-18 17:46 ` dpdklab
2024-07-18 17:49 ` dpdklab
2024-07-18 17:50 ` dpdklab
2024-07-18 17:50 ` dpdklab
2024-07-18 17:51 ` |SUCCESS| " dpdklab
2024-07-18 17:52 ` |PENDING| " dpdklab
2024-07-18 17:52 ` dpdklab
2024-07-18 17:56 ` dpdklab
2024-07-18 17:57 ` dpdklab
2024-07-18 18:03 ` dpdklab
2024-07-18 18:18 ` dpdklab
2024-07-18 18:26 ` dpdklab
2024-07-18 18:55 ` dpdklab
2024-07-18 19:10 ` dpdklab
2024-07-18 19:11 ` |SUCCESS| " dpdklab
2024-07-18 22:51 ` 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=669949ec.050a0220.c87f8.4dd4SMTPIN_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).