From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136937-136939 [PATCH] [v2,3/3] net/ionic: add vdev suppo
Date: Tue, 20 Feb 2024 21:58:22 -0800 (PST) [thread overview]
Message-ID: <65d590fe.620a0220.ef583.f10bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136939
_Functional Testing PASS_
Submitter: Boyer, Andrew <Andrew.Boyer@amd.com>
Date: Tuesday, February 20 2024 20:42:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa24b3f588b31ee9699f6b2dde8d12c0453448d1
136937-136939 --> 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/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29199/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-21 6:01 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 5:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 15:04 dpdklab
2024-02-21 7:26 dpdklab
2024-02-21 7:20 dpdklab
2024-02-21 6:24 dpdklab
2024-02-21 5:51 dpdklab
2024-02-21 5:23 dpdklab
2024-02-20 22:57 dpdklab
2024-02-20 22:35 dpdklab
2024-02-20 22:26 dpdklab
2024-02-20 22:25 dpdklab
2024-02-20 22:25 dpdklab
2024-02-20 22:23 dpdklab
2024-02-20 22:22 dpdklab
2024-02-20 22:17 dpdklab
2024-02-20 22:14 dpdklab
2024-02-20 22:13 dpdklab
2024-02-20 22:13 dpdklab
2024-02-20 22:12 dpdklab
2024-02-20 22:12 dpdklab
2024-02-20 22:12 dpdklab
2024-02-20 22:10 dpdklab
2024-02-20 22:09 dpdklab
2024-02-20 22:08 dpdklab
2024-02-20 22:08 dpdklab
2024-02-20 22:07 dpdklab
2024-02-20 22:07 dpdklab
2024-02-20 22:07 dpdklab
2024-02-20 22:06 dpdklab
2024-02-20 22:06 dpdklab
2024-02-20 22:05 dpdklab
2024-02-20 22:05 dpdklab
2024-02-20 22:05 dpdklab
2024-02-20 22:05 dpdklab
2024-02-20 22:05 dpdklab
2024-02-20 22:04 dpdklab
2024-02-20 22:04 dpdklab
2024-02-20 22:04 dpdklab
2024-02-20 22:03 dpdklab
2024-02-20 22:03 dpdklab
2024-02-20 22:03 dpdklab
2024-02-20 22:03 dpdklab
2024-02-20 22:02 dpdklab
2024-02-20 21:55 dpdklab
2024-02-20 21:54 dpdklab
2024-02-20 21:54 dpdklab
2024-02-20 21:53 dpdklab
2024-02-20 21:52 dpdklab
2024-02-20 21:52 dpdklab
2024-02-20 21:52 dpdklab
2024-02-20 21:52 dpdklab
2024-02-20 21:51 dpdklab
2024-02-20 21:51 dpdklab
2024-02-20 21:51 dpdklab
2024-02-20 21:51 dpdklab
2024-02-20 21:50 dpdklab
2024-02-20 21:49 dpdklab
2024-02-20 21:49 dpdklab
2024-02-20 21:48 dpdklab
2024-02-20 21:48 dpdklab
2024-02-20 21:48 dpdklab
2024-02-20 21:47 dpdklab
2024-02-20 21:46 dpdklab
2024-02-20 21:45 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=65d590fe.620a0220.ef583.f10bSMTPIN_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).