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| pw143451-143452 [PATCH] [2/2] net/nfp: flow rule supports
Date: Fri, 30 Aug 2024 04:01:05 -0700 (PDT)	[thread overview]
Message-ID: <66d1a671.050a0220.29b5c7.996cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240830031025.2422579-3-chaoyong.he@corigine.com>

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

_Functional Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Friday, August 30 2024 03:10:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:334bda1613888c26e6345dab3f2522e54087e808

143451-143452 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#177704

Test environment and result as below:

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/30882/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-30 11:01 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240830031025.2422579-3-chaoyong.he@corigine.com>
2024-08-30  2:46 ` |SUCCESS| pw143451-143452 [PATCH 2/2] net/nfp: flow rule supports match Ethernet type qemudev
2024-08-30  2:51 ` qemudev
2024-08-30  3:12 ` |SUCCESS| pw143452 " checkpatch
2024-08-30  4:03 ` |FAILURE| " 0-day Robot
2024-08-30  9:12 ` |SUCCESS| pw143451-143452 [PATCH] [2/2] net/nfp: flow rule supports dpdklab
2024-08-30  9:18 ` dpdklab
2024-08-30  9:21 ` dpdklab
2024-08-30  9:22 ` dpdklab
2024-08-30  9:29 ` |PENDING| " dpdklab
2024-08-30  9:30 ` |SUCCESS| " dpdklab
2024-08-30  9:32 ` dpdklab
2024-08-30  9:47 ` dpdklab
2024-08-30  9:49 ` dpdklab
2024-08-30  9:51 ` dpdklab
2024-08-30  9:51 ` dpdklab
2024-08-30  9:52 ` dpdklab
2024-08-30  9:53 ` dpdklab
2024-08-30  9:55 ` dpdklab
2024-08-30 10:00 ` dpdklab
2024-08-30 10:08 ` dpdklab
2024-08-30 10:09 ` dpdklab
2024-08-30 10:13 ` dpdklab
2024-08-30 10:16 ` |PENDING| " dpdklab
2024-08-30 10:20 ` |SUCCESS| " dpdklab
2024-08-30 10:20 ` dpdklab
2024-08-30 10:21 ` dpdklab
2024-08-30 10:21 ` dpdklab
2024-08-30 10:25 ` |WARNING| " dpdklab
2024-08-30 10:29 ` |FAILURE| " dpdklab
2024-08-30 10:30 ` dpdklab
2024-08-30 10:30 ` dpdklab
2024-08-30 10:30 ` |WARNING| " dpdklab
2024-08-30 10:31 ` dpdklab
2024-08-30 10:31 ` dpdklab
2024-08-30 10:33 ` |SUCCESS| " dpdklab
2024-08-30 10:33 ` dpdklab
2024-08-30 10:34 ` |FAILURE| " dpdklab
2024-08-30 10:35 ` dpdklab
2024-08-30 10:49 ` dpdklab
2024-08-30 10:56 ` dpdklab
2024-08-30 10:58 ` dpdklab
2024-08-30 11:01 ` dpdklab [this message]
2024-08-30 11:07 ` |SUCCESS| " dpdklab
2024-08-30 11:10 ` |WARNING| " dpdklab
2024-08-30 11:10 ` dpdklab
2024-08-30 11:51 ` |SUCCESS| " dpdklab
2024-08-30 11:57 ` |FAILURE| " dpdklab
2024-08-30 11:59 ` dpdklab
2024-08-30 12:00 ` dpdklab
2024-08-30 13:49 ` dpdklab
2024-09-19  7:41 ` |SUCCESS| " dpdklab
2024-09-19  8:00 ` dpdklab
2024-09-19  8:14 ` dpdklab
2024-09-19  8:33 ` 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=66d1a671.050a0220.29b5c7.996cSMTPIN_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).