automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw145028-145029 [PATCH v4 2/2] test/ipsec: add unit test for stateless processing
Date: Fri, 4 Oct 2024 14:11:11 +0800	[thread overview]
Message-ID: <202410040611.4946BBJ7181354@localhost.localdomain> (raw)
In-Reply-To: <20241004063443.179264-2-asasidharan@marvell.com>

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

_Compilation OK_

Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Fri, 4 Oct 2024 12:04:42 +0530
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 3b50d6c67a3c033a49739a0bd1a132aee6d9e324

145028-145029 --> 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-04  6:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241004063443.179264-2-asasidharan@marvell.com>
2024-10-04  6:11 ` qemudev [this message]
2024-10-04  6:15 ` qemudev
2024-10-04  6:36 ` |SUCCESS| pw145029 " checkpatch
2024-10-04  7:24 ` 0-day Robot
2024-10-04 16:30 ` |SUCCESS| pw145028-145029 [PATCH] [v4,2/2] test/ipsec: add unit test dpdklab
2024-10-04 16:31 ` |PENDING| " dpdklab
2024-10-04 16:48 ` |SUCCESS| " dpdklab
2024-10-04 16:49 ` dpdklab
2024-10-04 16:55 ` dpdklab
2024-10-04 16:57 ` dpdklab
2024-10-04 16:58 ` dpdklab
2024-10-04 17:08 ` dpdklab
2024-10-04 17:08 ` |PENDING| " dpdklab
2024-10-04 17:22 ` dpdklab
2024-10-04 17:27 ` |SUCCESS| " dpdklab
2024-10-04 17:39 ` dpdklab
2024-10-04 18:04 ` dpdklab
2024-10-04 18:12 ` dpdklab
2024-10-04 20:41 ` dpdklab
2024-10-04 21:20 ` dpdklab
2024-10-04 23:33 ` dpdklab
2024-10-05 13:34 ` 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=202410040611.4946BBJ7181354@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).