automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw151974-151976 [PATCH v5 3/3] app/test: add SM4 GCM tests
Date: Tue, 25 Feb 2025 00:25:26 +0800	[thread overview]
Message-ID: <202502241625.51OGPQlC1131477@localhost.localdomain> (raw)
In-Reply-To: <20250224165939.717714-3-brian.dooley@intel.com>

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

_Compilation OK_

Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Mon, 24 Feb 2025 16:59:37 +0000
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 95ff85f8acb0c7c912fd29b01428377fcbf1112a

151974-151976 --> 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:[~2025-02-24 17:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250224165939.717714-3-brian.dooley@intel.com>
2025-02-24 16:25 ` qemudev [this message]
2025-02-24 16:29 ` qemudev
2025-02-24 17:00 ` |SUCCESS| pw151976 " checkpatch
2025-02-24 19:24 ` 0-day Robot
2025-02-24 20:52 ` |SUCCESS| pw151974-151976 [PATCH] [v5,3/3] app/test: add SM4 GCM tes dpdklab
2025-02-24 20:54 ` dpdklab
2025-02-24 21:01 ` dpdklab
2025-02-24 21:16 ` dpdklab
2025-02-24 21:19 ` dpdklab
2025-02-24 21:20 ` dpdklab
2025-02-24 21:22 ` dpdklab
2025-02-24 21:26 ` dpdklab
2025-02-24 21:32 ` dpdklab
2025-02-24 21:44 ` dpdklab
2025-02-24 21:54 ` |PENDING| " dpdklab
2025-02-24 22:09 ` dpdklab
2025-02-24 22:17 ` dpdklab
2025-02-24 22:21 ` |SUCCESS| " dpdklab
2025-02-24 22:26 ` |PENDING| " dpdklab
2025-02-24 23:02 ` |SUCCESS| " dpdklab
2025-02-24 23:03 ` dpdklab
2025-02-24 23:03 ` dpdklab
2025-02-24 23:04 ` 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=202502241625.51OGPQlC1131477@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).