From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152938 [PATCH] net/gve: support for gVNIC PCI revision 1
Date: Tue, 15 Apr 2025 20:18:28 -0700 (PDT) [thread overview]
Message-ID: <67ff2184.050a0220.df597.117eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250416024421.722135-1-joshwash@google.com>
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152938
_Functional Testing PASS_
Submitter: Joshua Washington <joshwash@google.com>
Date: Wednesday, April 16 2025 02:44:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:35ff024be343391025e56697fd7f8931cc96fe3c
152938 --> functional testing pass
Upstream job id: Template-DPDK-DTS-Pipeline#249
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8.0-55-generic
Compiler: gcc 13.3.0
NIC: Mellanox ConnectX-5 100000 Mbps
Aggregate Results by Test Suite
+----------------------------------+--------+
| Test Suite | Result |
+==================================+========+
| TestBlocklist | PASS |
+----------------------------------+--------+
| TestPMDBufferScatter | PASS |
+----------------------------------+--------+
| TestPromiscSupport | PASS |
+----------------------------------+--------+
| TestUniPkt | PASS |
+----------------------------------+--------+
| TestDynamicConfig | PASS |
+----------------------------------+--------+
| TestHelloWorld | PASS |
+----------------------------------+--------+
| TestL2fwd | PASS |
+----------------------------------+--------+
| TestMacFilter | PASS |
+----------------------------------+--------+
| TestMTU | PASS |
+----------------------------------+--------+
| TestPortRestartConfigPersistency | PASS |
+----------------------------------+--------+
| TestSoftNIC | PASS |
+----------------------------------+--------+
| TestVLAN | PASS |
+----------------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33014/
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:[~2025-04-16 3:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250416024421.722135-1-joshwash@google.com>
2025-04-16 2:11 ` |SUCCESS| pw152938 [PATCH] net/gve: support for gVNIC PCI revision 1 and later qemudev
2025-04-16 2:16 ` qemudev
2025-04-16 2:44 ` checkpatch
2025-04-16 3:18 ` dpdklab [this message]
2025-04-16 3:19 ` |SUCCESS| pw152938 [PATCH] net/gve: support for gVNIC PCI revision 1 dpdklab
2025-04-16 3:25 ` |PENDING| " dpdklab
2025-04-16 3:29 ` dpdklab
2025-04-16 3:29 ` dpdklab
2025-04-16 3:35 ` |SUCCESS| " dpdklab
2025-04-16 3:39 ` dpdklab
2025-04-16 3:40 ` |PENDING| " dpdklab
2025-04-16 3:41 ` |SUCCESS| " dpdklab
2025-04-16 3:50 ` |PENDING| " dpdklab
2025-04-16 3:51 ` |SUCCESS| " dpdklab
2025-04-16 3:55 ` dpdklab
2025-04-16 4:03 ` |SUCCESS| pw152938 [PATCH] net/gve: support for gVNIC PCI revision 1 and later 0-day Robot
2025-04-16 4:07 ` |SUCCESS| pw152938 [PATCH] net/gve: support for gVNIC PCI revision 1 dpdklab
2025-04-16 4:09 ` dpdklab
2025-04-16 4:09 ` dpdklab
2025-04-16 4:24 ` dpdklab
2025-04-16 4:34 ` dpdklab
2025-04-16 4:36 ` dpdklab
2025-04-16 5:26 ` dpdklab
2025-04-16 8:22 ` dpdklab
2025-04-16 9:00 ` 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=67ff2184.050a0220.df597.117eSMTPIN_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).