automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138480 [PATCH] app/testpmd: fix releasing action handle flush memory
Date: Tue, 19 Mar 2024 17:09:50 +0800	[thread overview]
Message-ID: <202403190909.42J99oQS3142017@localhost.localdomain> (raw)
In-Reply-To: <20240319093249.307606-1-bingz@nvidia.com>

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

_Compilation OK_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Tue, 19 Mar 2024 11:32:49 +0200
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 20db7deeb5131e46e859e212b334e8bef88ae701

138480 --> 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-19  9:34 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240319093249.307606-1-bingz@nvidia.com>
2024-03-19  9:09 ` qemudev [this message]
2024-03-19  9:14 ` qemudev
2024-03-19  9:34 ` checkpatch
2024-03-19 10:24 ` 0-day Robot
2024-03-19 18:25 ` |SUCCESS| pw138480 [PATCH] app/testpmd: fix releasing action handle dpdklab
2024-03-19 18:44 ` dpdklab
2024-03-19 18:45 ` dpdklab
2024-03-19 18:50 ` dpdklab
2024-03-19 18:57 ` dpdklab
2024-03-19 18:58 ` dpdklab
2024-03-19 18:59 ` dpdklab
2024-03-19 19:02 ` dpdklab
2024-03-19 19:30 ` dpdklab
2024-03-19 19:34 ` dpdklab
2024-03-19 19:34 ` dpdklab
2024-03-19 19:36 ` dpdklab
2024-03-19 19:39 ` dpdklab
2024-03-19 19:43 ` dpdklab
2024-03-19 19:44 ` dpdklab
2024-03-19 19:46 ` dpdklab
2024-03-19 19:47 ` dpdklab
2024-03-19 19:48 ` dpdklab
2024-03-19 19:48 ` dpdklab
2024-03-19 19:48 ` dpdklab
2024-03-19 19:50 ` dpdklab
2024-03-19 19:52 ` dpdklab
2024-03-19 20:22 ` dpdklab
2024-03-19 20:23 ` dpdklab
2024-03-19 20:31 ` dpdklab
2024-03-19 20:31 ` dpdklab
2024-03-19 20:32 ` dpdklab
2024-03-19 20:33 ` dpdklab
2024-03-19 20:33 ` dpdklab
2024-03-19 20:33 ` dpdklab
2024-03-19 20:34 ` dpdklab
2024-03-19 20:34 ` dpdklab
2024-03-19 20:36 ` dpdklab
2024-03-19 20:36 ` dpdklab
2024-03-19 20:36 ` dpdklab
2024-03-19 20:37 ` dpdklab
2024-03-19 20:37 ` dpdklab
2024-03-19 20:37 ` dpdklab
2024-03-19 20:38 ` dpdklab
2024-03-19 20:38 ` dpdklab
2024-03-19 20:38 ` dpdklab
2024-03-19 20:39 ` dpdklab
2024-03-19 20:39 ` dpdklab
2024-03-19 20:39 ` dpdklab
2024-03-19 20:39 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:41 ` dpdklab
2024-03-19 20:41 ` dpdklab
2024-03-19 20:42 ` dpdklab
2024-03-19 20:42 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:53 ` dpdklab
2024-03-19 20:54 ` dpdklab
2024-03-19 20:55 ` dpdklab
2024-03-19 20:56 ` dpdklab
2024-03-19 21:02 ` dpdklab
2024-03-19 21:03 ` dpdklab
2024-03-19 21:06 ` dpdklab
2024-03-19 21:07 ` dpdklab
2024-03-19 21:46 ` dpdklab
2024-03-19 21:59 ` dpdklab
2024-03-19 23:05 ` dpdklab
2024-03-20 18:41 ` |WARNING| " dpdklab
2024-03-21 10:37 ` |SUCCESS| " dpdklab
2024-03-21 11: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=202403190909.42J99oQS3142017@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).