automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137794-137800 [PATCH v5 7/7] compress/nitrox: support stateful request
Date: Sat, 2 Mar 2024 17:16:54 +0800	[thread overview]
Message-ID: <202403020916.4229GsAq4127418@localhost.localdomain> (raw)
In-Reply-To: <20240302093813.14922-8-rnagadheeraj@marvell.com>

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

_Compilation OK_

Submitter: Nagadheeraj Rottela <rnagadheeraj@marvell.com>
Date: Sat, 2 Mar 2024 15:08:07 +0530
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 5ac50824383c2683c0dfdf24c6dc493f1fa54852

137794-137800 --> 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-02  9:41 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240302093813.14922-8-rnagadheeraj@marvell.com>
2024-03-02  9:16 ` qemudev [this message]
2024-03-02  9:21 ` qemudev
2024-03-02  9:40 ` |SUCCESS| pw137800 " checkpatch
2024-03-02 10:45 ` 0-day Robot
2024-03-02 19:15 ` |SUCCESS| pw137794-137800 [PATCH] [v5,7/7] compress/nitrox: support dpdklab
2024-03-02 19:16 ` dpdklab
2024-03-02 19:16 ` dpdklab
2024-03-02 19:18 ` dpdklab
2024-03-02 19:19 ` dpdklab
2024-03-02 19:20 ` dpdklab
2024-03-02 19:20 ` dpdklab
2024-03-02 19:21 ` dpdklab
2024-03-02 19:21 ` dpdklab
2024-03-02 19:21 ` dpdklab
2024-03-02 19:23 ` dpdklab
2024-03-02 19:24 ` dpdklab
2024-03-02 19:27 ` dpdklab
2024-03-02 19:30 ` dpdklab
2024-03-02 19:31 ` dpdklab
2024-03-02 19:31 ` dpdklab
2024-03-02 19:32 ` dpdklab
2024-03-02 19:35 ` dpdklab
2024-03-02 19:37 ` dpdklab
2024-03-02 19:37 ` dpdklab
2024-03-02 19:38 ` dpdklab
2024-03-02 19:39 ` dpdklab
2024-03-02 19:39 ` dpdklab
2024-03-02 19:40 ` dpdklab
2024-03-02 19:40 ` dpdklab
2024-03-02 19:41 ` dpdklab
2024-03-02 19:42 ` dpdklab
2024-03-02 19:42 ` dpdklab
2024-03-02 19:43 ` dpdklab
2024-03-02 19:44 ` dpdklab
2024-03-02 19:46 ` dpdklab
2024-03-02 19:46 ` dpdklab
2024-03-02 19:47 ` dpdklab
2024-03-02 19:47 ` dpdklab
2024-03-02 19:48 ` dpdklab
2024-03-02 19:50 ` dpdklab
2024-03-02 19:50 ` dpdklab
2024-03-02 19:51 ` dpdklab
2024-03-02 19:51 ` dpdklab
2024-03-02 19:51 ` dpdklab
2024-03-02 19:52 ` dpdklab
2024-03-02 19:53 ` dpdklab
2024-03-02 19:53 ` dpdklab
2024-03-02 19:54 ` dpdklab
2024-03-02 19:54 ` dpdklab
2024-03-02 19:54 ` dpdklab
2024-03-02 19:58 ` dpdklab
2024-03-02 19:58 ` dpdklab
2024-03-02 19:58 ` dpdklab
2024-03-02 19:59 ` dpdklab
2024-03-02 20:00 ` dpdklab
2024-03-02 20:00 ` dpdklab
2024-03-02 20:04 ` dpdklab
2024-03-02 20:06 ` dpdklab
2024-03-02 20:07 ` dpdklab
2024-03-02 20:08 ` dpdklab
2024-03-02 20:08 ` dpdklab
2024-03-02 20:08 ` dpdklab
2024-03-02 20:16 ` dpdklab
2024-03-02 20:17 ` dpdklab
2024-03-02 20:19 ` dpdklab
2024-03-02 20:20 ` dpdklab
2024-03-02 20:30 ` dpdklab
2024-03-02 20:44 ` dpdklab
2024-03-02 20:44 ` dpdklab
2024-03-02 20:53 ` dpdklab
2024-03-02 21:32 ` dpdklab
2024-03-02 21:49 ` dpdklab
2024-03-02 22:51 ` dpdklab
2024-03-03  5:13 ` dpdklab
2024-03-06 14:34 ` dpdklab
2024-03-06 15:09 ` dpdklab
2024-03-06 15:36 ` 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=202403020916.4229GsAq4127418@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).