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| pw153143 [PATCH] [v2] trace: fix out of bounds write in __
Date: Thu, 24 Apr 2025 20:30:47 -0700 (PDT)	[thread overview]
Message-ID: <680b01e7.0d0a0220.414c8.7a9dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250424170818.23970-1-oleksandrn@interfacemasters.com>

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

_Functional Testing PASS_

Submitter: Oleksandr Nahnybida <oleksandrn@interfacemasters.com>
Date: Thursday, April 24 2025 17:08:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ca1690ebd224f148268285b15b97441ccdbdd07e

153143 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#222926

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-04-25  3:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250424170818.23970-1-oleksandrn@interfacemasters.com>
2025-04-24 16:43 ` |SUCCESS| pw153143 [PATCH v2] trace: fix out of bounds write in __rte_trace_mem_get qemudev
2025-04-24 16:47 ` qemudev
2025-04-24 17:09 ` checkpatch
2025-04-24 18:24 ` 0-day Robot
2025-04-25  3:18 ` |SUCCESS| pw153143 [PATCH] [v2] trace: fix out of bounds write in __ dpdklab
2025-04-25  3:26 ` |PENDING| " dpdklab
2025-04-25  3:30 ` dpdklab
2025-04-25  3:30 ` dpdklab [this message]
2025-04-25  3:33 ` |SUCCESS| " dpdklab
2025-04-25  3:38 ` |PENDING| " dpdklab
2025-04-25  3:38 ` |SUCCESS| " dpdklab
2025-04-25  3:39 ` dpdklab
2025-04-25  3:57 ` |PENDING| " dpdklab
2025-04-25  3:57 ` |SUCCESS| " dpdklab
2025-04-25  3:58 ` dpdklab
2025-04-25  5:08 ` dpdklab
2025-04-25  5:45 ` dpdklab
2025-04-25  5:50 ` dpdklab
2025-04-25  6:04 ` dpdklab
2025-04-25  6:21 ` dpdklab
2025-04-25  7:58 ` 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=680b01e7.0d0a0220.414c8.7a9dSMTPIN_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).