From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138209 [PATCH] [v2,1/1] net/mana: add vlan tagging suppo
Date: Tue, 12 Mar 2024 03:58:40 -0700 (PDT) [thread overview]
Message-ID: <65f03560.050a0220.b2456.d5f5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240312093611.359025-1-weh@linux.microsoft.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138209
_Functional Testing PASS_
Submitter: Wei Hu <weh@linux.microsoft.com>
Date: Tuesday, March 12 2024 09:36:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e3faaed01e14ffdfe8f4190030540ed874184b55
138209 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29514/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-12 10:58 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240312093611.359025-1-weh@linux.microsoft.com>
2024-03-12 9:18 ` |SUCCESS| pw138209 [PATCH v2 1/1] net/mana: add vlan tagging support qemudev
2024-03-12 9:23 ` qemudev
2024-03-12 9:43 ` |WARNING| " checkpatch
2024-03-12 10:40 ` |SUCCESS| pw138209 [PATCH] [v2,1/1] net/mana: add vlan tagging suppo dpdklab
2024-03-12 10:40 ` dpdklab
2024-03-12 10:41 ` dpdklab
2024-03-12 10:42 ` dpdklab
2024-03-12 10:42 ` dpdklab
2024-03-12 10:42 ` |SUCCESS| pw138209 [PATCH v2 1/1] net/mana: add vlan tagging support 0-day Robot
2024-03-12 10:44 ` |SUCCESS| pw138209 [PATCH] [v2,1/1] net/mana: add vlan tagging suppo dpdklab
2024-03-12 10:44 ` dpdklab
2024-03-12 10:48 ` dpdklab
2024-03-12 10:49 ` dpdklab
2024-03-12 10:49 ` dpdklab
2024-03-12 10:58 ` dpdklab [this message]
2024-03-12 10:59 ` dpdklab
2024-03-12 10:59 ` dpdklab
2024-03-12 10:59 ` dpdklab
2024-03-12 11:00 ` dpdklab
2024-03-12 11:01 ` dpdklab
2024-03-12 11:01 ` dpdklab
2024-03-12 11:02 ` dpdklab
2024-03-12 11:02 ` dpdklab
2024-03-12 11:02 ` dpdklab
2024-03-12 11:02 ` dpdklab
2024-03-12 11:03 ` dpdklab
2024-03-12 11:03 ` dpdklab
2024-03-12 11:03 ` dpdklab
2024-03-12 11:03 ` dpdklab
2024-03-12 11:03 ` dpdklab
2024-03-12 11:04 ` dpdklab
2024-03-12 11:04 ` dpdklab
2024-03-12 11:05 ` dpdklab
2024-03-12 11:07 ` dpdklab
2024-03-12 11:07 ` dpdklab
2024-03-12 11:08 ` dpdklab
2024-03-12 11:08 ` dpdklab
2024-03-12 11:08 ` dpdklab
2024-03-12 11:09 ` dpdklab
2024-03-12 11:09 ` dpdklab
2024-03-12 11:09 ` dpdklab
2024-03-12 11:09 ` dpdklab
2024-03-12 11:09 ` dpdklab
2024-03-12 11:09 ` dpdklab
2024-03-12 11:10 ` dpdklab
2024-03-12 11:10 ` dpdklab
2024-03-12 11:10 ` dpdklab
2024-03-12 11:10 ` dpdklab
2024-03-12 11:10 ` dpdklab
2024-03-12 11:10 ` dpdklab
2024-03-12 11:10 ` dpdklab
2024-03-12 11:11 ` dpdklab
2024-03-12 11:11 ` dpdklab
2024-03-12 11:11 ` dpdklab
2024-03-12 11:13 ` dpdklab
2024-03-12 11:14 ` dpdklab
2024-03-12 11:14 ` dpdklab
2024-03-12 11:15 ` dpdklab
2024-03-12 11:15 ` dpdklab
2024-03-12 11:15 ` dpdklab
2024-03-12 11:16 ` dpdklab
2024-03-12 11:16 ` dpdklab
2024-03-12 11:16 ` dpdklab
2024-03-12 11:18 ` dpdklab
2024-03-12 11:18 ` dpdklab
2024-03-12 11:31 ` dpdklab
2024-03-12 11:31 ` dpdklab
2024-03-12 11:34 ` dpdklab
2024-03-12 11:41 ` dpdklab
2024-03-12 11:41 ` dpdklab
2024-03-12 12:21 ` dpdklab
2024-03-15 21:16 ` dpdklab
2024-03-15 21:52 ` 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=65f03560.050a0220.b2456.d5f5SMTPIN_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).