automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147388-147399 [PATCH v17 14/14] app/test: add cryptodev test for zsda
Date: Sat, 26 Oct 2024 23:55:42 +0800	[thread overview]
Message-ID: <202410261555.49QFtgLx1433435@localhost.localdomain> (raw)
In-Reply-To: <20241026161502.2348307-13-li.hanxiao@zte.com.cn>

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

_Compilation OK_

Submitter: Hanxiao Li <li.hanxiao@zte.com.cn>
Date: Sun, 27 Oct 2024 00:12:31 +0800
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 3ee7a3e0e0e0f5a81a4b102a834697bc488fb32f

147388-147399 --> 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-26 16:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241026161502.2348307-13-li.hanxiao@zte.com.cn>
2024-10-26 15:55 ` qemudev [this message]
2024-10-26 16:00 ` qemudev
2024-10-26 16:21 ` |SUCCESS| pw147399 " checkpatch
2024-10-26 17:26 ` 0-day Robot
2024-10-27  6:35 ` |SUCCESS| pw147388-147399 [PATCH] [v17,14/14] app/test: add cryptode dpdklab
2024-10-27  6:50 ` dpdklab
2024-10-27  6:53 ` dpdklab
2024-10-27  6:58 ` dpdklab
2024-10-27  7:02 ` dpdklab
2024-10-27  7:08 ` dpdklab
2024-10-27 10:46 ` |PENDING| " dpdklab
2024-10-27 11:13 ` |SUCCESS| " dpdklab
2024-10-27 19:27 ` dpdklab
2024-10-27 20:03 ` dpdklab
2024-10-29 16:21 ` dpdklab
2024-10-30  3:25 ` dpdklab
2024-10-30  8:10 ` dpdklab
2024-10-30  8:10 ` dpdklab
2024-10-31 20:15 ` dpdklab
2024-11-01 14: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=202410261555.49QFtgLx1433435@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).