From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129156 [PATCH] [v2] net/idpf: refine vport parameter str
Date: Fri, 30 Jun 2023 16:10:06 -0700 (PDT) [thread overview]
Message-ID: <649f60ce.050a0220.bd192.e705SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/129156
_Functional Testing PASS_
Submitter: Liu, Mingxia <mingxia.liu@intel.com>
Date: Friday, June 30 2023 18:51:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:93a4b3beba4ee611685148917981f846427cafb2
129156 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.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/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26891/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-30 23:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 23:10 dpdklab [this message]
2023-06-30 23:12 dpdklab
2023-06-30 23:15 dpdklab
2023-06-30 23:17 dpdklab
2023-06-30 23:19 dpdklab
2023-06-30 23:20 dpdklab
2023-06-30 23:21 dpdklab
2023-06-30 23:32 dpdklab
2023-07-01 0:05 dpdklab
2023-07-01 0:05 dpdklab
2023-07-01 0:06 dpdklab
2023-07-01 0:12 dpdklab
2023-07-01 0:24 dpdklab
2023-07-01 0:25 dpdklab
2023-07-01 0:29 dpdklab
2023-07-01 0:29 dpdklab
2023-07-01 0:33 dpdklab
2023-07-01 0:36 dpdklab
2023-07-01 0:43 dpdklab
2023-07-01 3:52 dpdklab
2023-07-01 4:09 dpdklab
2023-07-01 4:11 dpdklab
2023-07-01 8:50 dpdklab
2023-07-01 9:03 dpdklab
2023-07-01 9:41 dpdklab
2023-07-01 9:51 dpdklab
2023-07-01 10:22 dpdklab
2023-07-02 16: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=649f60ce.050a0220.bd192.e705SMTPIN_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).