From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138960 [PATCH] maintainers: update for testpmd
Date: Tue, 02 Apr 2024 10:52:34 -0700 (PDT) [thread overview]
Message-ID: <660c45e2.020a0220.3c4e8.b129SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240328161021.1346192-1-yuying.zhang@intel.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138960
_Functional Testing PASS_
Submitter: Zhang, Yuying <yuying.zhang@intel.com>
Date: Thursday, March 28 2024 16:10:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a9778aad62470a38ccbb4e09a2a6bf0cc2e0e36d
138960 --> functional testing pass
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
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 22.04 ARM
Kernel: 5.15.83+
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/29678/
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-04-02 17:52 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240328161021.1346192-1-yuying.zhang@intel.com>
2024-03-28 16:01 ` qemudev
2024-03-28 16:05 ` qemudev
2024-03-28 16:11 ` checkpatch
2024-03-28 16:50 ` dpdklab
2024-03-28 16:58 ` dpdklab
2024-03-28 16:59 ` dpdklab
2024-03-28 16:59 ` dpdklab
2024-03-28 16:59 ` dpdklab
2024-03-28 17:00 ` dpdklab
2024-03-28 17:00 ` dpdklab
2024-03-28 17:00 ` dpdklab
2024-03-28 17:00 ` dpdklab
2024-03-28 17:01 ` dpdklab
2024-03-28 17:01 ` dpdklab
2024-03-28 17:01 ` dpdklab
2024-03-28 17:03 ` dpdklab
2024-03-28 17:06 ` 0-day Robot
2024-03-28 17:06 ` dpdklab
2024-03-28 17:06 ` dpdklab
2024-03-28 17:07 ` dpdklab
2024-03-28 17:07 ` dpdklab
2024-03-28 17:08 ` dpdklab
2024-03-28 17:08 ` dpdklab
2024-03-28 17:08 ` dpdklab
2024-03-28 17:08 ` dpdklab
2024-03-28 17:08 ` dpdklab
2024-03-28 17:09 ` dpdklab
2024-03-28 17:09 ` dpdklab
2024-03-28 17:09 ` dpdklab
2024-03-28 17:09 ` dpdklab
2024-03-28 17:09 ` dpdklab
2024-03-28 17:10 ` dpdklab
2024-03-28 17:10 ` dpdklab
2024-03-28 17:11 ` dpdklab
2024-03-28 17:11 ` dpdklab
2024-03-28 17:11 ` dpdklab
2024-03-28 17:12 ` dpdklab
2024-03-28 17:13 ` dpdklab
2024-03-28 17:13 ` dpdklab
2024-03-28 17:13 ` dpdklab
2024-03-28 17:14 ` dpdklab
2024-03-28 17:14 ` dpdklab
2024-03-28 17:15 ` dpdklab
2024-03-28 17:15 ` dpdklab
2024-03-28 17:16 ` dpdklab
2024-03-28 17:16 ` dpdklab
2024-03-28 17:16 ` dpdklab
2024-03-28 17:17 ` dpdklab
2024-03-28 17:18 ` dpdklab
2024-03-28 17:18 ` dpdklab
2024-03-28 17:18 ` dpdklab
2024-03-28 17:19 ` dpdklab
2024-03-28 17:19 ` dpdklab
2024-03-28 17:19 ` dpdklab
2024-03-28 17:19 ` dpdklab
2024-03-28 17:20 ` dpdklab
2024-03-28 17:22 ` dpdklab
2024-03-28 17:22 ` dpdklab
2024-03-28 17:24 ` dpdklab
2024-03-28 17:24 ` dpdklab
2024-03-28 17:24 ` dpdklab
2024-03-28 17:25 ` dpdklab
2024-03-28 17:26 ` dpdklab
2024-03-28 17:26 ` dpdklab
2024-03-28 17:27 ` dpdklab
2024-03-28 17:28 ` dpdklab
2024-03-28 17:30 ` dpdklab
2024-03-28 17:32 ` dpdklab
2024-03-28 17:33 ` dpdklab
2024-03-28 17:33 ` dpdklab
2024-03-28 17:34 ` dpdklab
2024-03-28 17:34 ` dpdklab
2024-03-28 17:35 ` dpdklab
2024-03-28 17:35 ` dpdklab
2024-03-28 17:37 ` dpdklab
2024-03-28 17:37 ` dpdklab
2024-03-28 17:39 ` dpdklab
2024-03-28 17:40 ` dpdklab
2024-03-28 17:43 ` dpdklab
2024-03-28 17:50 ` dpdklab
2024-03-28 17:54 ` dpdklab
2024-03-28 18:02 ` dpdklab
2024-03-28 18:05 ` dpdklab
2024-03-28 18:13 ` dpdklab
2024-03-28 18:34 ` dpdklab
2024-03-28 18:38 ` dpdklab
2024-03-28 18:49 ` dpdklab
2024-04-02 17:48 ` dpdklab
2024-04-02 17:52 ` dpdklab [this message]
2024-04-02 17:56 ` dpdklab
2024-04-02 18:16 ` dpdklab
2024-04-02 18:20 ` 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=660c45e2.020a0220.3c4e8.b129SMTPIN_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).