automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140291 [PATCH v2] test/crypto: fix enqueue dequeue callback case
Date: Thu, 23 May 2024 20:22:35 +0800	[thread overview]
Message-ID: <202405231222.44NCMZqi1751692@localhost.localdomain> (raw)
In-Reply-To: <20240523124838.3474899-1-gakhil@marvell.com>

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

_Compilation OK_

Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Thu, 23 May 2024 18:18:38 +0530
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 6f80df8cb0f889203d7cd27766abcc6ebc720e33

140291 --> 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


       reply	other threads:[~2024-05-23 12:51 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240523124838.3474899-1-gakhil@marvell.com>
2024-05-23 12:22 ` qemudev [this message]
2024-05-23 12:27 ` qemudev
2024-05-23 12:48 ` checkpatch
2024-05-23 13:44 ` 0-day Robot
2024-05-23 16:14 ` |SUCCESS| pw140291 [PATCH] [v2] test/crypto: fix enqueue dequeue cal dpdklab
2024-05-23 16:17 ` dpdklab
2024-05-23 16:18 ` dpdklab
2024-05-23 16:19 ` dpdklab
2024-05-23 16:20 ` dpdklab
2024-05-23 16:49 ` dpdklab
2024-05-23 16:51 ` dpdklab
2024-05-23 16:51 ` dpdklab
2024-05-23 16:52 ` dpdklab
2024-05-23 16:52 ` dpdklab
2024-05-23 16:53 ` dpdklab
2024-05-23 16:53 ` dpdklab
2024-05-23 16:53 ` dpdklab
2024-05-23 16:53 ` dpdklab
2024-05-23 16:53 ` dpdklab
2024-05-23 16:54 ` dpdklab
2024-05-23 16:54 ` dpdklab
2024-05-23 16:54 ` dpdklab
2024-05-23 16:55 ` dpdklab
2024-05-23 16:55 ` dpdklab
2024-05-23 16:55 ` dpdklab
2024-05-23 16:55 ` dpdklab
2024-05-23 16:55 ` dpdklab
2024-05-23 16:56 ` dpdklab
2024-05-23 16:56 ` dpdklab
2024-05-23 16:56 ` dpdklab
2024-05-23 16:56 ` dpdklab
2024-05-23 16:56 ` dpdklab
2024-05-23 16:56 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:57 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:58 ` dpdklab
2024-05-23 16:59 ` dpdklab
2024-05-23 16:59 ` dpdklab
2024-05-23 16:59 ` dpdklab
2024-05-23 16:59 ` dpdklab
2024-05-23 16:59 ` dpdklab
2024-05-23 17:00 ` dpdklab
2024-05-23 17:00 ` dpdklab
2024-05-23 17:00 ` dpdklab
2024-05-23 17:01 ` dpdklab
2024-05-23 17:01 ` dpdklab
2024-05-23 17:01 ` dpdklab
2024-05-23 17:01 ` dpdklab
2024-05-23 17:01 ` dpdklab
2024-05-23 17:02 ` dpdklab
2024-05-23 17:02 ` dpdklab
2024-05-23 17:02 ` dpdklab
2024-05-23 17:02 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:03 ` dpdklab
2024-05-23 17:04 ` dpdklab
2024-05-23 17:04 ` dpdklab
2024-05-23 17:05 ` dpdklab
2024-05-23 17:05 ` dpdklab
2024-05-23 17:07 ` dpdklab
2024-05-23 17:07 ` dpdklab
2024-05-23 17:07 ` dpdklab
2024-05-23 17:07 ` dpdklab
2024-05-23 17:09 ` dpdklab
2024-05-23 17:10 ` dpdklab
2024-05-23 17:12 ` dpdklab
2024-05-23 17:14 ` dpdklab
2024-05-23 17:15 ` dpdklab
2024-05-23 17:19 ` dpdklab
2024-05-23 17:21 ` dpdklab
2024-05-23 17:21 ` dpdklab
2024-05-23 17:25 ` dpdklab
2024-05-23 17:33 ` dpdklab
2024-05-23 17:36 ` dpdklab
2024-05-23 17:51 ` dpdklab
2024-05-23 17:57 ` dpdklab
2024-05-23 17:57 ` 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=202405231222.44NCMZqi1751692@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).