automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138306 [PATCH v2] app/test: fix rsa tests in qat suite
Date: Wed, 13 Mar 2024 16:51:34 +0800	[thread overview]
Message-ID: <202403130851.42D8pY0j4126002@localhost.localdomain> (raw)
In-Reply-To: <20240313091347.25207-1-arkadiuszx.kusztal@intel.com>

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

_Compilation OK_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wed, 13 Mar 2024 09:13:47 +0000
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: a86f381b826660e88794754c41d3aec79ce9b87c

138306 --> 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-13  9:16 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240313091347.25207-1-arkadiuszx.kusztal@intel.com>
2024-03-13  8:51 ` qemudev [this message]
2024-03-13  8:55 ` qemudev
2024-03-13  9:14 ` checkpatch
2024-03-13  9:56 ` |SUCCESS| pw138306 [PATCH] [v2] " dpdklab
2024-03-13  9:57 ` |FAILURE| " dpdklab
2024-03-13  9:58 ` dpdklab
2024-03-13  9:58 ` |SUCCESS| " dpdklab
2024-03-13  9:59 ` dpdklab
2024-03-13  9:59 ` |FAILURE| " dpdklab
2024-03-13 10:07 ` |SUCCESS| " dpdklab
2024-03-13 10:07 ` |FAILURE| " dpdklab
2024-03-13 10:07 ` |SUCCESS| " dpdklab
2024-03-13 10:07 ` dpdklab
2024-03-13 10:08 ` dpdklab
2024-03-13 10:08 ` dpdklab
2024-03-13 10:08 ` dpdklab
2024-03-13 10:08 ` dpdklab
2024-03-13 10:09 ` dpdklab
2024-03-13 10:09 ` dpdklab
2024-03-13 10:09 ` dpdklab
2024-03-13 10:09 ` |FAILURE| " dpdklab
2024-03-13 10:09 ` |SUCCESS| " dpdklab
2024-03-13 10:09 ` |FAILURE| " dpdklab
2024-03-13 10:10 ` |SUCCESS| " dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` |FAILURE| " dpdklab
2024-03-13 10:10 ` |SUCCESS| " dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:10 ` dpdklab
2024-03-13 10:11 ` |FAILURE| " dpdklab
2024-03-13 10:12 ` |SUCCESS| " dpdklab
2024-03-13 10:12 ` dpdklab
2024-03-13 10:13 ` dpdklab
2024-03-13 10:13 ` dpdklab
2024-03-13 10:13 ` dpdklab
2024-03-13 10:13 ` |FAILURE| " dpdklab
2024-03-13 10:13 ` |SUCCESS| " dpdklab
2024-03-13 10:13 ` dpdklab
2024-03-13 10:14 ` dpdklab
2024-03-13 10:14 ` |FAILURE| " dpdklab
2024-03-13 10:14 ` |SUCCESS| " dpdklab
2024-03-13 10:14 ` dpdklab
2024-03-13 10:14 ` dpdklab
2024-03-13 10:14 ` dpdklab
2024-03-13 10:15 ` dpdklab
2024-03-13 10:15 ` dpdklab
2024-03-13 10:15 ` dpdklab
2024-03-13 10:15 ` dpdklab
2024-03-13 10:16 ` |FAILURE| " dpdklab
2024-03-13 10:16 ` |SUCCESS| " dpdklab
2024-03-13 10:16 ` dpdklab
2024-03-13 10:16 ` dpdklab
2024-03-13 10:16 ` dpdklab
2024-03-13 10:16 ` dpdklab
2024-03-13 10:16 ` dpdklab
2024-03-13 10:17 ` |SUCCESS| pw138306 [PATCH v2] " 0-day Robot
2024-03-13 10:17 ` |SUCCESS| pw138306 [PATCH] [v2] " dpdklab
2024-03-13 10:17 ` dpdklab
2024-03-13 10:17 ` dpdklab
2024-03-13 10:17 ` dpdklab
2024-03-13 10:17 ` dpdklab
2024-03-13 10:18 ` dpdklab
2024-03-13 10:19 ` dpdklab
2024-03-13 10:19 ` dpdklab
2024-03-13 10:19 ` dpdklab
2024-03-13 10:19 ` dpdklab
2024-03-13 10:35 ` dpdklab
2024-03-13 10:35 ` |FAILURE| " dpdklab
2024-03-13 10:40 ` |SUCCESS| " dpdklab
2024-03-13 11:24 ` dpdklab
2024-03-16 22:57 ` dpdklab
2024-03-16 23:33 ` 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=202403130851.42D8pY0j4126002@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).