automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126098 [PATCH] test/crypto: fix return value for snow3g testcase
Date: Fri, 14 Apr 2023 21:47:07 +0800	[thread overview]
Message-ID: <202304141347.33EDl72u1584851@localhost.localdomain> (raw)
In-Reply-To: <20230414135526.4271-1-saoirse.odonovan@intel.com>

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

_Compilation OK_

Submitter: Saoirse O'Donovan <saoirse.odonovan@intel.com>
Date: Fri, 14 Apr 2023 13:55:26 +0000
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 189c02f5ec891ed02927062e124e8ca03adf74e7

126098 --> 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:[~2023-04-14 14:01 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230414135526.4271-1-saoirse.odonovan@intel.com>
2023-04-14 13:47 ` qemudev [this message]
2023-04-14 13:51 ` qemudev
2023-04-14 13:57 ` checkpatch
2023-04-14 14:59 ` 0-day Robot
2023-04-14 15:58 dpdklab
2023-04-14 15:59 dpdklab
2023-04-14 16:04 dpdklab
2023-04-14 16:05 dpdklab
2023-04-14 16:06 dpdklab
2023-04-14 16:07 dpdklab
2023-04-14 16:10 dpdklab
2023-04-14 16:11 dpdklab
2023-04-14 16:19 dpdklab
2023-04-14 16:23 dpdklab
2023-04-14 16:44 dpdklab
2023-04-14 16:51 dpdklab
2023-04-14 16:51 dpdklab
2023-04-14 16:54 dpdklab
2023-04-14 16:55 dpdklab
2023-04-14 16:55 dpdklab
2023-04-14 16:58 dpdklab
2023-04-14 17:03 dpdklab
2023-04-14 17:12 dpdklab
2023-04-14 17:15 dpdklab
2023-04-14 17:24 dpdklab
2023-04-14 17:26 dpdklab
2023-04-14 17:28 dpdklab
2023-04-14 17:29 dpdklab
2023-04-14 17:32 dpdklab
2023-04-14 17:34 dpdklab
2023-04-14 17:34 dpdklab
2023-04-14 17:36 dpdklab
2023-04-14 17:37 dpdklab
2023-04-14 17:39 dpdklab
2023-04-14 17:44 dpdklab
2023-04-14 17:59 dpdklab
2023-04-14 18:07 dpdklab
2023-04-14 18:09 dpdklab
2023-04-14 18:20 dpdklab
2023-04-14 18:20 dpdklab
2023-04-14 18:25 dpdklab
2023-04-14 18:26 dpdklab
2023-04-14 18:28 dpdklab
2023-04-14 18:29 dpdklab
2023-04-14 18:31 dpdklab
2023-04-14 18:35 dpdklab
2023-04-14 19:07 dpdklab
2023-04-14 20:52 dpdklab
2023-04-14 20:57 dpdklab
2023-04-14 23:06 dpdklab
2023-04-15  0:16 dpdklab
2023-04-15  2:32 dpdklab
2023-04-15  2:47 dpdklab
2023-04-15  2:52 dpdklab
2023-04-15  2:57 dpdklab
2023-04-15  3:13 dpdklab
2023-04-15  3:17 dpdklab
2023-04-15  4:21 dpdklab
2023-04-15  5:48 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=202304141347.33EDl72u1584851@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).