automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw154574-154576 [PATCH 3/3] test/crypto: set ptr to null post crypto op free
Date: Tue, 24 Jun 2025 21:45:30 +0800	[thread overview]
Message-ID: <202506241345.55ODjUJn1733475@localhost.localdomain> (raw)
In-Reply-To: <20250618125410.767919-4-nkaithakadan@marvell.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/154576

_Compilation OK RETEST #1_

Submitter: Nithinsen Kaithakadan <nkaithakadan@marvell.com>
Date: Wed, 18 Jun 2025 12:54:07 +0000
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 6890ee7ba76e92745d6c61b3b6b9d757ebaaa89d

154574-154576 --> meson & ninja build successfully

Test environment and result as below:

+---------------------+----------------+
|     Environment     | compilation    |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS           |
+---------------------+----------------+

Loongnix-Server 8.3
    Kernel: 4.19.190+
    Compiler: gcc 8.3


  parent reply	other threads:[~2025-06-24 14:21 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250618125410.767919-4-nkaithakadan@marvell.com>
2025-06-18 12:23 ` qemudev
2025-06-18 12:28 ` qemudev
2025-06-18 12:54 ` |SUCCESS| pw154576 " checkpatch
2025-06-18 14:25 ` 0-day Robot
2025-06-18 17:20 ` |SUCCESS| pw154574-154576 [PATCH] [3/3] test/crypto: set ptr to null dpdklab
2025-06-18 17:23 ` dpdklab
2025-06-18 17:31 ` dpdklab
2025-06-18 18:00 ` dpdklab
2025-06-18 18:30 ` dpdklab
2025-06-18 18:49 ` |PENDING| " dpdklab
2025-06-18 18:53 ` |SUCCESS| " dpdklab
2025-06-18 19:19 ` dpdklab
2025-06-18 19:22 ` |PENDING| " dpdklab
2025-06-18 19:34 ` dpdklab
2025-06-18 20:03 ` |SUCCESS| " dpdklab
2025-06-18 20:03 ` dpdklab
2025-06-18 20:48 ` dpdklab
2025-06-18 20:50 ` dpdklab
2025-06-18 20:50 ` dpdklab
2025-06-18 20:56 ` |FAILURE| " dpdklab
2025-06-18 21:09 ` dpdklab
2025-06-19  0:22 ` dpdklab
2025-06-19  0:22 ` dpdklab
2025-06-19  2:03 ` |SUCCESS| " dpdklab
2025-06-19  4:06 ` dpdklab
2025-06-19  4:49 ` dpdklab
2025-06-19 23:42 ` |FAILURE| " dpdklab
2025-06-19 23:53 ` dpdklab
2025-06-20 13:55 ` |SUCCESS| " dpdklab
2025-06-24 13:45 ` qemudev [this message]
2025-06-24 13:50 ` |SUCCESS| pw154574-154576 [PATCH 3/3] test/crypto: set ptr to null post crypto op free qemudev
2025-06-24 18:15 ` |SUCCESS| pw154574-154576 [PATCH] [3/3] test/crypto: set ptr to null dpdklab
2025-06-24 19:22 ` |PENDING| " dpdklab
2025-06-24 20:04 ` |SUCCESS| " dpdklab
2025-06-24 20:20 ` |PENDING| " dpdklab
2025-06-24 20:46 ` |SUCCESS| " dpdklab
2025-06-24 20:54 ` dpdklab
2025-06-24 22:48 ` dpdklab
2025-06-24 23:11 ` dpdklab
2025-06-24 23:37 ` |PENDING| " dpdklab
2025-06-25  0:00 ` |SUCCESS| " dpdklab
2025-06-25  0:03 ` dpdklab
2025-06-25  0:19 ` dpdklab
2025-06-25  2:14 ` dpdklab
2025-06-25  2:16 ` dpdklab
2025-06-25  2:16 ` dpdklab
2025-06-25  2:17 ` dpdklab
2025-06-25  2:17 ` dpdklab
2025-06-25  2:17 ` dpdklab
2025-06-25  2:17 ` dpdklab
2025-06-25  2:19 ` dpdklab
2025-06-25  2:20 ` dpdklab
2025-06-25  2:20 ` dpdklab
2025-06-25  2:21 ` dpdklab
2025-06-25  2:21 ` dpdklab
2025-06-25  3:11 ` dpdklab
2025-06-25  3:43 ` |PENDING| " dpdklab
2025-06-25  4:17 ` |WARNING| " dpdklab
2025-06-25  5:00 ` dpdklab
2025-06-25  5:03 ` dpdklab
2025-06-25  5:25 ` |SUCCESS| " 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=202506241345.55ODjUJn1733475@localhost.localdomain \
    --to=qemudev@loongson.cn \
    --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).