From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138229-138249 [PATCH v3 21/21] test/security: add out of place sgl test case for TLS 1.2
Date: Wed, 13 Mar 2024 01:31:59 +0800 [thread overview]
Message-ID: <202403121731.42CHVxp43684791@localhost.localdomain> (raw)
In-Reply-To: <20240312175143.1664699-22-asasidharan@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138249
_Compilation OK_
Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Tue, 12 Mar 2024 23:21:23 +0530
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: a86f381b826660e88794754c41d3aec79ce9b87c
138229-138249 --> 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-03-12 17:57 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240312175143.1664699-22-asasidharan@marvell.com>
2024-03-12 17:31 ` qemudev [this message]
2024-03-12 17:36 ` qemudev
2024-03-12 17:56 ` |SUCCESS| pw138249 " checkpatch
2024-03-12 18:43 ` |FAILURE| " 0-day Robot
2024-03-12 19:53 ` |SUCCESS| pw138229-138249 [PATCH] [v3,21/21] test/security: add out dpdklab
2024-03-12 19:54 ` dpdklab
2024-03-12 19:55 ` dpdklab
2024-03-12 19:55 ` dpdklab
2024-03-12 19:55 ` dpdklab
2024-03-12 19:56 ` dpdklab
2024-03-12 19:56 ` dpdklab
2024-03-12 19:56 ` dpdklab
2024-03-12 19:56 ` dpdklab
2024-03-12 19:56 ` dpdklab
2024-03-12 19:57 ` dpdklab
2024-03-12 19:57 ` dpdklab
2024-03-12 19:57 ` dpdklab
2024-03-12 19:57 ` dpdklab
2024-03-12 20:13 ` dpdklab
2024-03-12 20:16 ` dpdklab
2024-03-12 20:17 ` dpdklab
2024-03-12 20:17 ` dpdklab
2024-03-12 20:19 ` dpdklab
2024-03-12 20:20 ` dpdklab
2024-03-12 20:22 ` dpdklab
2024-03-12 20:22 ` dpdklab
2024-03-12 20:40 ` dpdklab
2024-03-12 20:40 ` dpdklab
2024-03-12 20:51 ` |WARNING| " dpdklab
2024-03-12 20:53 ` dpdklab
2024-03-12 21:07 ` dpdklab
2024-03-12 21:07 ` dpdklab
2024-03-12 21:08 ` dpdklab
2024-03-12 21:09 ` dpdklab
2024-03-12 21:09 ` |SUCCESS| " dpdklab
2024-03-12 21:10 ` dpdklab
2024-03-12 21:10 ` dpdklab
2024-03-12 21:10 ` dpdklab
2024-03-12 21:11 ` dpdklab
2024-03-12 21:11 ` dpdklab
2024-03-12 21:11 ` dpdklab
2024-03-12 21:11 ` dpdklab
2024-03-12 21:12 ` dpdklab
2024-03-12 21:12 ` |WARNING| " dpdklab
2024-03-12 21:12 ` |SUCCESS| " dpdklab
2024-03-12 21:12 ` |WARNING| " dpdklab
2024-03-12 21:13 ` |SUCCESS| " dpdklab
2024-03-12 21:13 ` dpdklab
2024-03-12 21:13 ` dpdklab
2024-03-12 21:13 ` dpdklab
2024-03-12 21:13 ` dpdklab
2024-03-12 21:14 ` dpdklab
2024-03-12 21:14 ` dpdklab
2024-03-12 21:14 ` |WARNING| " dpdklab
2024-03-12 21:14 ` |SUCCESS| " dpdklab
2024-03-12 21:14 ` dpdklab
2024-03-12 21:15 ` dpdklab
2024-03-12 21:15 ` dpdklab
2024-03-12 21:15 ` dpdklab
2024-03-12 21:15 ` dpdklab
2024-03-12 21:15 ` dpdklab
2024-03-12 21:16 ` dpdklab
2024-03-12 21:16 ` dpdklab
2024-03-12 21:16 ` dpdklab
2024-03-12 21:17 ` dpdklab
2024-03-12 21:17 ` dpdklab
2024-03-12 21:18 ` dpdklab
2024-03-12 21:28 ` dpdklab
2024-03-12 21:31 ` dpdklab
2024-03-12 21:41 ` dpdklab
2024-03-12 21:42 ` dpdklab
2024-03-12 21:49 ` |WARNING| " dpdklab
2024-03-12 22:02 ` |SUCCESS| " dpdklab
2024-03-12 22:23 ` dpdklab
2024-03-12 22:36 ` dpdklab
2024-03-12 23:36 ` dpdklab
2024-03-16 8:40 ` dpdklab
2024-03-16 9:16 ` 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=202403121731.42CHVxp43684791@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).