automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138178-138198 [PATCH v2 21/21] test/security: add out of place sgl test case for TLS 1.2
Date: Tue, 12 Mar 2024 14:59:33 +0800	[thread overview]
Message-ID: <202403120659.42C6xXOm2881600@localhost.localdomain> (raw)
In-Reply-To: <20240312071805.1354530-22-asasidharan@marvell.com>

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

_Compilation OK_

Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Tue, 12 Mar 2024 12:47:45 +0530
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: a86f381b826660e88794754c41d3aec79ce9b87c

138178-138198 --> 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-03-12  7:24 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240312071805.1354530-22-asasidharan@marvell.com>
2024-03-12  6:59 ` qemudev [this message]
2024-03-12  7:04 ` qemudev
2024-03-12  7:20 ` |SUCCESS| pw138198 " checkpatch
2024-03-12  7:50 ` |SUCCESS| pw138178-138198 [PATCH] [v2,21/21] test/security: add out dpdklab
2024-03-12  8:13 ` dpdklab
2024-03-12  8:14 ` dpdklab
2024-03-12  8:15 ` dpdklab
2024-03-12  8:15 ` dpdklab
2024-03-12  8:16 ` dpdklab
2024-03-12  8:17 ` dpdklab
2024-03-12  8:18 ` dpdklab
2024-03-12  8:19 ` dpdklab
2024-03-12  8:19 ` dpdklab
2024-03-12  8:20 ` dpdklab
2024-03-12  8:21 ` dpdklab
2024-03-12  8:21 ` dpdklab
2024-03-12  8:22 ` dpdklab
2024-03-12  8:22 ` dpdklab
2024-03-12  8:22 ` |SUCCESS| pw138198 [PATCH v2 21/21] test/security: add out of place sgl test case for TLS 1.2 0-day Robot
2024-03-12  8:22 ` |SUCCESS| pw138178-138198 [PATCH] [v2,21/21] test/security: add out dpdklab
2024-03-12  8:23 ` dpdklab
2024-03-12  8:23 ` dpdklab
2024-03-12  8:24 ` dpdklab
2024-03-12  8:24 ` dpdklab
2024-03-12  8:25 ` dpdklab
2024-03-12  8:26 ` dpdklab
2024-03-12  8:26 ` dpdklab
2024-03-12  8:26 ` dpdklab
2024-03-12  8:26 ` dpdklab
2024-03-12  8:26 ` dpdklab
2024-03-12  8:27 ` dpdklab
2024-03-12  8:27 ` dpdklab
2024-03-12  8:27 ` dpdklab
2024-03-12  8:27 ` dpdklab
2024-03-12  8:27 ` dpdklab
2024-03-12  8:27 ` |WARNING| " dpdklab
2024-03-12  8:28 ` dpdklab
2024-03-12  8:28 ` |SUCCESS| " dpdklab
2024-03-12  8:28 ` dpdklab
2024-03-12  8:28 ` dpdklab
2024-03-12  8:29 ` dpdklab
2024-03-12  8:29 ` dpdklab
2024-03-12  8:29 ` dpdklab
2024-03-12  8:29 ` |WARNING| " dpdklab
2024-03-12  8:30 ` |SUCCESS| " dpdklab
2024-03-12  8:30 ` dpdklab
2024-03-12  8:30 ` dpdklab
2024-03-12  8:30 ` |WARNING| " dpdklab
2024-03-12  8:31 ` |SUCCESS| " dpdklab
2024-03-12  8:31 ` dpdklab
2024-03-12  8:31 ` |WARNING| " dpdklab
2024-03-12  8:32 ` |SUCCESS| " dpdklab
2024-03-12  8:32 ` dpdklab
2024-03-12  8:32 ` |WARNING| " dpdklab
2024-03-12  8:32 ` |SUCCESS| " dpdklab
2024-03-12  8:33 ` dpdklab
2024-03-12  8:33 ` dpdklab
2024-03-12  8:33 ` dpdklab
2024-03-12  8:33 ` dpdklab
2024-03-12  8:33 ` dpdklab
2024-03-12  8:33 ` |WARNING| " dpdklab
2024-03-12  8:34 ` |SUCCESS| " dpdklab
2024-03-12  8:34 ` |WARNING| " dpdklab
2024-03-12  8:34 ` dpdklab
2024-03-12  8:34 ` |SUCCESS| " dpdklab
2024-03-12  8:34 ` dpdklab
2024-03-12  8:34 ` dpdklab
2024-03-12  8:35 ` dpdklab
2024-03-12  8:38 ` |WARNING| " dpdklab
2024-03-12  8:42 ` |SUCCESS| " dpdklab
2024-03-12  9:48 ` dpdklab
2024-03-15 17:27 ` dpdklab
2024-03-15 18:03 ` 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=202403120659.42C6xXOm2881600@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).