From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153800 [PATCH] [v2] drivers: remove __rte_used from func
Date: Tue, 27 May 2025 16:03:58 -0700 (PDT) [thread overview]
Message-ID: <683644de.050a0220.2be2fb.03bdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1748375344-10254-1-git-send-email-andremue@linux.microsoft.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/153800
_Functional Testing PASS_
Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Tuesday, May 27 2025 19:49:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:966c5e0e85be233606a1be882079222a01075717
153800 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#227858
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 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/33259/
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-05-27 23:04 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1748375344-10254-1-git-send-email-andremue@linux.microsoft.com>
2025-05-27 19:21 ` |SUCCESS| pw153800 [PATCH v2] drivers: remove __rte_used from functions for compatibility with MSVC qemudev
2025-05-27 19:25 ` qemudev
2025-05-27 19:48 ` checkpatch
2025-05-27 21:03 ` 0-day Robot
2025-05-27 21:43 ` |SUCCESS| pw153800 [PATCH] [v2] drivers: remove __rte_used from func dpdklab
2025-05-27 21:55 ` dpdklab
2025-05-27 22:04 ` dpdklab
2025-05-27 22:05 ` dpdklab
2025-05-27 22:42 ` dpdklab
2025-05-27 22:43 ` dpdklab
2025-05-27 22:49 ` |PENDING| " dpdklab
2025-05-27 22:55 ` |SUCCESS| " dpdklab
2025-05-27 22:55 ` |PENDING| " dpdklab
2025-05-27 22:57 ` |SUCCESS| " dpdklab
2025-05-27 23:03 ` dpdklab [this message]
2025-05-27 23:09 ` |PENDING| " dpdklab
2025-05-27 23:22 ` |SUCCESS| " dpdklab
2025-05-27 23:30 ` dpdklab
2025-05-27 23:35 ` dpdklab
2025-05-27 23:39 ` |PENDING| " dpdklab
2025-05-27 23:45 ` |SUCCESS| " dpdklab
2025-05-28 0:03 ` |PENDING| " dpdklab
2025-05-28 0:08 ` |SUCCESS| " dpdklab
2025-05-28 0:16 ` |PENDING| " dpdklab
2025-05-28 0:37 ` |SUCCESS| " dpdklab
2025-05-28 0:39 ` dpdklab
2025-05-28 0:52 ` |PENDING| " dpdklab
2025-05-28 1:06 ` |WARNING| " dpdklab
2025-05-28 1:20 ` dpdklab
2025-05-28 1:23 ` dpdklab
2025-05-28 1:23 ` dpdklab
2025-05-28 1:27 ` dpdklab
2025-05-28 1:43 ` dpdklab
2025-05-28 1:52 ` |SUCCESS| " dpdklab
2025-05-28 1:56 ` dpdklab
2025-05-28 2:57 ` |WARNING| " dpdklab
2025-05-28 3:15 ` |SUCCESS| " dpdklab
2025-05-28 3:23 ` dpdklab
2025-05-28 3:53 ` |WARNING| " dpdklab
2025-05-28 4:16 ` |SUCCESS| " dpdklab
2025-05-28 4:21 ` dpdklab
2025-05-28 4:58 ` dpdklab
2025-05-28 8:20 ` dpdklab
2025-05-28 17:18 ` |WARNING| " dpdklab
2025-06-03 20:20 ` |SUCCESS| " dpdklab
2025-06-03 20:22 ` dpdklab
2025-06-04 3:22 ` dpdklab
2025-06-04 3:39 ` 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=683644de.050a0220.2be2fb.03bdSMTPIN_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).