From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw155108 [PATCH] [v1,1/1] net/iavf: fix order of inclusion
Date: Wed, 09 Jul 2025 08:18:10 -0700 (PDT) [thread overview]
Message-ID: <686e8832.630a0220.3d8c1d.76bbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <552f8241f4f65fce0c8b43797612a97dec5d9ebc.1752066381.git.anatoly.burakov@intel.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/155108
_Functional Testing PASS_
Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: Wednesday, July 09 2025 13:06:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f1853a0cc95eaae5842b88be0cbcd5becc2e94b7
155108 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#236064
Test environment and result as below:
Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel Corporation 4xxx Series QAT 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33627/
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-07-09 15:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <552f8241f4f65fce0c8b43797612a97dec5d9ebc.1752066381.git.anatoly.burakov@intel.com>
2025-07-09 12:31 ` |SUCCESS| pw155108 [PATCH v1 1/1] net/iavf: fix order of inclusion in vector code qemudev
2025-07-09 12:36 ` qemudev
2025-07-09 13:05 ` checkpatch
2025-07-09 15:16 ` |SUCCESS| pw155108 [PATCH] [v1,1/1] net/iavf: fix order of inclusion dpdklab
2025-07-09 15:18 ` dpdklab [this message]
2025-07-09 15:21 ` dpdklab
2025-07-09 16:00 ` |PENDING| " dpdklab
2025-07-09 16:00 ` |SUCCESS| " dpdklab
2025-07-09 16:13 ` |PENDING| " dpdklab
2025-07-09 16:19 ` dpdklab
2025-07-09 16:20 ` dpdklab
2025-07-09 16:52 ` dpdklab
2025-07-09 17:09 ` |SUCCESS| " dpdklab
2025-07-09 17:27 ` dpdklab
2025-07-09 18:02 ` dpdklab
2025-07-09 18:03 ` dpdklab
2025-07-09 18:33 ` |WARNING| " dpdklab
2025-07-09 19:41 ` |SUCCESS| " dpdklab
2025-07-10 0:20 ` |WARNING| " dpdklab
2025-07-10 0:53 ` dpdklab
2025-07-10 6:44 ` |SUCCESS| " dpdklab
2025-07-10 7:02 ` 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=686e8832.630a0220.3d8c1d.76bbSMTPIN_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).