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| pw154633-154634 [PATCH] [v2,2/2] common/cnxk: fix null poi
Date: Mon, 23 Jun 2025 06:46:38 -0700 (PDT)	[thread overview]
Message-ID: <68595abe.050a0220.158a3e.b31dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250623044907.2906896-2-rbhansali@marvell.com>

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

_Functional Testing PASS RETEST #1_

Submitter: Rahul Bhansali <rbhansali@marvell.com>
Date: Monday, June 23 2025 04:49:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6890ee7ba76e92745d6c61b3b6b9d757ebaaa89d

154633-154634 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#232471

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
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/33480/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-06-23 13:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250623044907.2906896-2-rbhansali@marvell.com>
2025-06-23  4:15 ` |SUCCESS| pw154633-154634 [PATCH v2 2/2] common/cnxk: fix null pointer checks qemudev
2025-06-23  4:19 ` qemudev
2025-06-23  4:49 ` |SUCCESS| pw154634 " checkpatch
2025-06-23  5:44 ` 0-day Robot
2025-06-23  6:18 ` |SUCCESS| pw154633-154634 [PATCH] [v2,2/2] common/cnxk: fix null poi dpdklab
2025-06-23  6:29 ` |PENDING| " dpdklab
2025-06-23  6:33 ` |SUCCESS| " dpdklab
2025-06-23  6:53 ` dpdklab
2025-06-23  6:59 ` |FAILURE| " dpdklab
2025-06-23  7:00 ` dpdklab
2025-06-23  7:03 ` |PENDING| " dpdklab
2025-06-23  7:10 ` |FAILURE| " dpdklab
2025-06-23  7:15 ` |SUCCESS| " dpdklab
2025-06-23  7:17 ` |FAILURE| " dpdklab
2025-06-23  7:24 ` |SUCCESS| " dpdklab
2025-06-23  7:31 ` dpdklab
2025-06-23  8:30 ` dpdklab
2025-06-23  8:36 ` |FAILURE| " dpdklab
2025-06-23  8:47 ` |PENDING| " dpdklab
2025-06-23  9:18 ` |FAILURE| " dpdklab
2025-06-23  9:57 ` |SUCCESS| " dpdklab
2025-06-23 10:18 ` dpdklab
2025-06-23 10:37 ` dpdklab
2025-06-23 13:14 ` |PENDING| " dpdklab
2025-06-23 13:15 ` |SUCCESS| " dpdklab
2025-06-23 13:25 ` |PENDING| " dpdklab
2025-06-23 13:30 ` dpdklab
2025-06-23 13:30 ` |SUCCESS| " dpdklab
2025-06-23 13:46 ` dpdklab [this message]
2025-06-23 13:51 ` |PENDING| " dpdklab
2025-06-23 13:53 ` |SUCCESS| " dpdklab
2025-06-23 14:04 ` |PENDING| " dpdklab
2025-06-23 14:17 ` |SUCCESS| " dpdklab
2025-06-23 14:24 ` dpdklab
2025-06-23 14:32 ` dpdklab
2025-06-23 15:29 ` dpdklab
2025-06-23 15:35 ` |WARNING| " 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=68595abe.050a0220.158a3e.b31dSMTPIN_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).