automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138655 [PATCH v3] app/test: fix rsa tests in qat suite
Date: Thu, 21 Mar 2024 16:23:24 +0800	[thread overview]
Message-ID: <202403210823.42L8NNNY636452@localhost.localdomain> (raw)
In-Reply-To: <20240321083502.30552-1-arkadiuszx.kusztal@intel.com>

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

_Compilation OK_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Thu, 21 Mar 2024 08:35:02 +0000
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 7f82e9c89f3514715533feb34f46ff1ea95c6f98

138655 --> 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-03-21  8:48 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240321083502.30552-1-arkadiuszx.kusztal@intel.com>
2024-03-21  8:23 ` qemudev [this message]
2024-03-21  8:28 ` qemudev
2024-03-21  8:36 ` checkpatch
2024-03-21  9:24 ` 0-day Robot
2024-03-21 10:37 ` |SUCCESS| pw138655 [PATCH] [v3] " dpdklab
2024-03-21 10:43 ` dpdklab
2024-03-21 10:56 ` dpdklab
2024-03-21 10:56 ` dpdklab
2024-03-21 11:10 ` dpdklab
2024-03-21 11:11 ` dpdklab
2024-03-21 11:13 ` dpdklab
2024-03-21 11:15 ` dpdklab
2024-03-21 11:17 ` dpdklab
2024-03-21 11:18 ` dpdklab
2024-03-21 11:20 ` dpdklab
2024-03-21 11:35 ` dpdklab
2024-03-21 11:38 ` dpdklab
2024-03-21 11:38 ` dpdklab
2024-03-21 11:39 ` dpdklab
2024-03-21 11:39 ` dpdklab
2024-03-21 11:39 ` dpdklab
2024-03-21 11:39 ` dpdklab
2024-03-21 11:42 ` dpdklab
2024-03-21 11:42 ` dpdklab
2024-03-21 11:42 ` dpdklab
2024-03-21 11:43 ` dpdklab
2024-03-21 12:25 ` dpdklab
2024-03-21 12:33 ` dpdklab
2024-03-21 12:33 ` dpdklab
2024-03-21 12:40 ` dpdklab
2024-03-21 12:43 ` dpdklab
2024-03-21 12:43 ` dpdklab
2024-03-21 12:43 ` dpdklab
2024-03-21 12:45 ` dpdklab
2024-03-21 12:46 ` dpdklab
2024-03-21 12:46 ` dpdklab
2024-03-21 12:46 ` dpdklab
2024-03-21 12:46 ` dpdklab
2024-03-21 12:47 ` dpdklab
2024-03-21 12:47 ` dpdklab
2024-03-21 12:47 ` dpdklab
2024-03-21 12:48 ` dpdklab
2024-03-21 12:48 ` dpdklab
2024-03-21 12:48 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:49 ` dpdklab
2024-03-21 12:50 ` dpdklab
2024-03-21 12:50 ` dpdklab
2024-03-21 12:50 ` dpdklab
2024-03-21 12:50 ` dpdklab
2024-03-21 12:50 ` dpdklab
2024-03-21 12:51 ` dpdklab
2024-03-21 12:51 ` dpdklab
2024-03-21 12:52 ` dpdklab
2024-03-21 12:52 ` dpdklab
2024-03-21 12:53 ` dpdklab
2024-03-21 12:53 ` dpdklab
2024-03-21 12:54 ` dpdklab
2024-03-21 12:55 ` dpdklab
2024-03-21 12:55 ` dpdklab
2024-03-21 12:56 ` dpdklab
2024-03-21 12:56 ` dpdklab
2024-03-21 12:57 ` dpdklab
2024-03-21 12:57 ` dpdklab
2024-03-21 12:58 ` dpdklab
2024-03-21 12:58 ` dpdklab
2024-03-21 12:58 ` dpdklab
2024-03-21 12:58 ` dpdklab
2024-03-21 12:58 ` dpdklab
2024-03-21 13:06 ` dpdklab
2024-03-21 15:04 ` dpdklab
2024-03-21 16:04 ` dpdklab
2024-03-21 16:17 ` dpdklab
2024-03-22  1:44 ` dpdklab
2024-03-23  8:35 ` dpdklab
2024-03-23  9:11 ` 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=202403210823.42L8NNNY636452@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).