automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153833 [PATCH] [v3] drivers: remove __rte_used from func
Date: Wed, 28 May 2025 22:47:20 -0700 (PDT)	[thread overview]
Message-ID: <6837f4e8.170a0220.1aa7b5.2273SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1748438571-20477-1-git-send-email-andremue@linux.microsoft.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/153833

_Functional Testing PASS_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Wednesday, May 28 2025 13:22:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d0f30081805b9b798a059dd26287436018888064

153833 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#228226

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/33270/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-05-29  5:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1748438571-20477-1-git-send-email-andremue@linux.microsoft.com>
2025-05-28 12:49 ` |SUCCESS| pw153833 [PATCH v3] drivers: remove __rte_used from functions for compatibility with MSVC qemudev
2025-05-28 12:53 ` qemudev
2025-05-28 13:23 ` checkpatch
2025-05-28 14:44 ` 0-day Robot
2025-05-29  5:05 ` |SUCCESS| pw153833 [PATCH] [v3] drivers: remove __rte_used from func dpdklab
2025-05-29  5:47 ` dpdklab [this message]
2025-05-29  6:53 ` |PENDING| " dpdklab
2025-05-29  6:56 ` |SUCCESS| " dpdklab
2025-05-29  7:21 ` dpdklab
2025-05-29  7:23 ` dpdklab
2025-05-29  7:24 ` dpdklab
2025-05-29  7:24 ` dpdklab
2025-05-29  7:25 ` dpdklab
2025-05-29  7:30 ` |PENDING| " dpdklab
2025-05-29  7:31 ` dpdklab
2025-05-29  7:50 ` dpdklab
2025-05-29  8:07 ` |SUCCESS| " dpdklab
2025-05-29 11:16 ` |WARNING| " dpdklab
2025-05-29 11:53 ` |SUCCESS| " dpdklab
2025-05-29 13:12 ` dpdklab
2025-05-29 17:48 ` |WARNING| " dpdklab
2025-05-30 10:18 ` |SUCCESS| " dpdklab
2025-05-30 14:42 ` |WARNING| " dpdklab
2025-05-30 16:08 ` |SUCCESS| " dpdklab
2025-05-30 16:39 ` dpdklab
2025-06-04  9:53 ` 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=6837f4e8.170a0220.1aa7b5.2273SMTPIN_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).