automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw131973 [PATCH] test/pdcp: add data walkthrough test
Date: Wed, 27 Sep 2023 00:23:14 +0800	[thread overview]
Message-ID: <202309261623.38QGNEYm2521696@localhost.localdomain> (raw)
In-Reply-To: <20230926163617.2166471-1-asasidharan@marvell.com>

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

_Compilation OK_

Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Tue, 26 Sep 2023 22:06:17 +0530
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: d419c85a7299a57fb94edcc00f1d2f816e22fb40

131973 --> 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-09-26 16:44 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230926163617.2166471-1-asasidharan@marvell.com>
2023-09-26 16:23 ` qemudev [this message]
2023-09-26 16:27 ` qemudev
2023-09-26 16:37 ` checkpatch
2023-09-26 21:09 dpdklab
2023-09-26 21:10 dpdklab
2023-09-26 21:11 dpdklab
2023-09-26 21:11 dpdklab
2023-09-26 21:11 dpdklab
2023-09-26 21:11 dpdklab
2023-09-26 21:12 dpdklab
2023-09-26 21:13 dpdklab
2023-09-26 21:13 dpdklab
2023-09-26 21:13 dpdklab
2023-09-26 21:13 dpdklab
2023-09-26 21:14 dpdklab
2023-09-26 21:14 dpdklab
2023-09-26 21:15 dpdklab
2023-09-26 21:15 dpdklab
2023-09-26 21:15 dpdklab
2023-09-26 21:16 dpdklab
2023-09-26 21:16 dpdklab
2023-09-26 21:16 dpdklab
2023-09-26 21:17 dpdklab
2023-09-26 21:19 dpdklab
2023-09-26 21:20 dpdklab
2023-09-26 21:21 dpdklab
2023-09-26 21:21 dpdklab
2023-09-26 21:28 dpdklab
2023-09-26 21:28 dpdklab
2023-09-26 21:29 dpdklab
2023-09-26 21:35 dpdklab
2023-09-26 21:44 dpdklab
2023-09-26 21:59 dpdklab
2023-09-26 22:01 dpdklab
2023-09-26 22:43 dpdklab
2023-09-26 22:50 dpdklab
2023-09-26 22:50 dpdklab
2023-09-26 22:51 dpdklab
2023-09-26 22:52 dpdklab
2023-09-26 22:52 dpdklab
2023-09-26 23:02 dpdklab
2023-09-26 23:02 dpdklab
2023-09-26 23:04 dpdklab
2023-09-26 23:13 dpdklab
2023-09-26 23:15 dpdklab
2023-09-26 23:16 dpdklab
2023-09-26 23:22 dpdklab
2023-09-26 23:23 dpdklab
2023-09-26 23:23 dpdklab
2023-09-26 23:26 dpdklab
2023-09-26 23:27 dpdklab
2023-09-26 23:29 dpdklab
2023-09-27  3:58 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=202309261623.38QGNEYm2521696@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).