From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw149231-149232 [PATCH v1 2/2] app/test: add SM4 GCM tests
Date: Fri, 13 Dec 2024 20:27:15 +0800 [thread overview]
Message-ID: <202412131227.4BDCRFed117913@localhost.localdomain> (raw)
In-Reply-To: <20241213125850.2714328-2-brian.dooley@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/149232
_Compilation OK_
Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Fri, 13 Dec 2024 12:58:48 +0000
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 7df61db6c387703a36306c1aea92225921e2eeb2
149231-149232 --> 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
next parent reply other threads:[~2024-12-13 13:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241213125850.2714328-2-brian.dooley@intel.com>
2024-12-13 12:27 ` qemudev [this message]
2024-12-13 12:31 ` qemudev
2024-12-13 13:00 ` |SUCCESS| pw149232 " checkpatch
2024-12-13 14:02 ` |FAILURE| " 0-day Robot
2024-12-13 22:31 ` |SUCCESS| pw149231-149232 [PATCH] [v1,2/2] app/test: add SM4 GCM tes dpdklab
2024-12-13 22:35 ` dpdklab
2024-12-13 22:40 ` dpdklab
2024-12-13 23:02 ` dpdklab
2024-12-13 23:09 ` dpdklab
2024-12-14 0:06 ` dpdklab
2024-12-14 0:46 ` |FAILURE| " dpdklab
2024-12-14 0:47 ` |PENDING| " dpdklab
2024-12-14 0:48 ` |FAILURE| " dpdklab
2024-12-14 0:54 ` dpdklab
2024-12-14 1:05 ` |SUCCESS| " dpdklab
2024-12-14 1:27 ` |PENDING| " dpdklab
2024-12-14 2:08 ` |WARNING| " dpdklab
2024-12-14 2:28 ` dpdklab
2024-12-14 2:48 ` |SUCCESS| " dpdklab
2024-12-14 3:37 ` |WARNING| " 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=202412131227.4BDCRFed117913@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).