automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw146906-146908 [PATCH v7 3/3] app/test: add test sm2 C1/Kp test cases
Date: Wed, 23 Oct 2024 17:03:12 +0800	[thread overview]
Message-ID: <202410230903.49N93CSL516638@localhost.localdomain> (raw)
In-Reply-To: <20241023081934.84997-4-arkadiuszx.kusztal@intel.com>

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

_Compilation OK_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wed, 23 Oct 2024 09:19:32 +0100
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 3ee7a3e0e0e0f5a81a4b102a834697bc488fb32f

146906-146908 --> 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-10-23  9:36 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241023081934.84997-4-arkadiuszx.kusztal@intel.com>
2024-10-23  9:03 ` qemudev [this message]
2024-10-23  9:07 ` qemudev
2024-10-23  9:36 ` |SUCCESS| pw146908 " checkpatch
2024-10-23 10:27 ` 0-day Robot
2024-10-23 19:49 ` |SUCCESS| pw146906-146908 [PATCH] [v7,3/3] app/test: add test sm2 C1 dpdklab
2024-10-23 20:04 ` dpdklab
2024-10-23 20:41 ` dpdklab
2024-10-23 21:08 ` dpdklab
2024-10-23 21:27 ` dpdklab
2024-10-23 21:55 ` dpdklab
2024-10-23 22:24 ` dpdklab
2024-10-23 22:54 ` dpdklab
2024-10-24  0:51 ` dpdklab
2024-10-24  1:26 ` dpdklab
2024-10-24  6:36 ` |FAILURE| " dpdklab
2024-10-24  6:37 ` dpdklab
2024-10-24  6:48 ` |WARNING| " dpdklab
2024-10-24  7:32 ` |PENDING| " dpdklab
2024-10-24  7:39 ` dpdklab
2024-10-24  8:37 ` |FAILURE| " dpdklab
2024-10-24  9:44 ` |SUCCESS| " dpdklab
2024-10-24 11:06 ` dpdklab
2024-10-24 11:25 ` |FAILURE| " dpdklab
2024-10-24 11:53 ` dpdklab
2024-10-24 12:06 ` |PENDING| " dpdklab
2024-10-24 12:39 ` |SUCCESS| " dpdklab
2024-10-24 12:41 ` |FAILURE| " dpdklab
2024-10-24 12:42 ` dpdklab
2024-10-24 12:54 ` |SUCCESS| " dpdklab
2024-10-24 13:22 ` dpdklab
2024-10-24 13:34 ` dpdklab
2024-10-24 14:02 ` |FAILURE| " dpdklab
2024-10-24 14:11 ` |SUCCESS| " dpdklab
2024-10-24 16:02 ` dpdklab
2024-10-27  9:39 ` dpdklab
2024-10-27 10:11 ` dpdklab
2024-10-29 22:37 ` |FAILURE| " dpdklab
2024-10-29 22:37 ` dpdklab
2024-10-29 22:38 ` dpdklab
2024-10-30 20:11 ` dpdklab
2024-10-31  5:13 ` dpdklab
2024-11-02  3:23 ` |SUCCESS| " dpdklab
2024-11-02  3:58 ` dpdklab
2024-11-03 14:36 ` dpdklab
2024-11-03 15:53 ` 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=202410230903.49N93CSL516638@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).