From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152566 [PATCH] [v1] maintainers: update for iavf and i40
Date: Thu, 27 Mar 2025 14:46:28 -0700 (PDT) [thread overview]
Message-ID: <67e5c734.170a0220.2c8339.1bbfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250326133010.168470-1-ian.stokes@intel.com>
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152566
_Functional Testing PASS_
Submitter: Ian Stokes <ian.stokes@intel.com>
Date: Wednesday, March 26 2025 13:30:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa3aca8a525decfd12bd5fa01ebc98789d5f7278
152566 --> functional testing pass
Upstream job id: Template-New-DTS-pipeline#4104
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8.0-55-generic
Compiler: gcc 13.3.0
NIC: Arm Mellanox ConnectX-5 100000 Mbps
Aggregate Results by Test Suite
+----------------------+--------+
| Test Suite | Result |
+======================+========+
| TestBlocklist | PASS |
+----------------------+--------+
| TestPMDBufferScatter | PASS |
+----------------------+--------+
| TestPromiscSupport | PASS |
+----------------------+--------+
| TestUniPkt | PASS |
+----------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32886/
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-03-27 21:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250326133010.168470-1-ian.stokes@intel.com>
2025-03-26 12:57 ` |SUCCESS| pw152566 [PATCH v1] maintainers: update for iavf and i40e qemudev
2025-03-26 13:01 ` qemudev
2025-03-26 13:31 ` checkpatch
2025-03-26 14:43 ` 0-day Robot
2025-03-26 16:29 ` |PENDING| pw152566 [PATCH] [v1] maintainers: update for iavf and i40 dpdklab
2025-03-26 16:31 ` dpdklab
2025-03-26 16:33 ` |SUCCESS| " dpdklab
2025-03-26 16:36 ` dpdklab
2025-03-26 16:37 ` |PENDING| " dpdklab
2025-03-26 16:41 ` dpdklab
2025-03-26 16:51 ` |SUCCESS| " dpdklab
2025-03-26 17:00 ` dpdklab
2025-03-26 17:06 ` dpdklab
2025-03-26 17:09 ` dpdklab
2025-03-26 17:10 ` dpdklab
2025-03-26 17:10 ` dpdklab
2025-03-26 17:13 ` dpdklab
2025-03-26 17:25 ` dpdklab
2025-03-26 17:59 ` dpdklab
2025-03-26 18:33 ` dpdklab
2025-03-26 18:35 ` dpdklab
2025-03-27 21:46 ` dpdklab [this message]
2025-03-27 22:29 ` 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=67e5c734.170a0220.2c8339.1bbfSMTPIN_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).