automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138049 [PATCH] app/dma-perf: calrify incorrect NUMA config
Date: Wed, 6 Mar 2024 22:56:35 +0800	[thread overview]
Message-ID: <202403061456.426EuZec3233196@localhost.localdomain> (raw)
In-Reply-To: <20240306150204.1375-1-vipin.varghese@amd.com>

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

_Compilation OK_

Submitter: Vipin Varghese <vipin.varghese@amd.com>
Date: Wed, 6 Mar 2024 20:32:04 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: d74543f8ad30db164c08ec69910b05d6811b1b89

138049 --> 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-06 15:21 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240306150204.1375-1-vipin.varghese@amd.com>
2024-03-06 14:56 ` qemudev [this message]
2024-03-06 15:00 ` qemudev
2024-03-06 15:03 ` checkpatch
2024-03-06 16:04 ` 0-day Robot
2024-03-06 17:59 ` |SUCCESS| pw138049 [PATCH] app/dma-perf: calrify incorrect NUMA conf dpdklab
2024-03-06 18:02 ` dpdklab
2024-03-06 18:03 ` dpdklab
2024-03-06 18:05 ` dpdklab
2024-03-06 18:11 ` dpdklab
2024-03-06 18:12 ` dpdklab
2024-03-06 18:13 ` dpdklab
2024-03-06 18:25 ` dpdklab
2024-03-06 18:25 ` dpdklab
2024-03-06 18:25 ` dpdklab
2024-03-06 18:26 ` dpdklab
2024-03-06 18:27 ` dpdklab
2024-03-06 18:28 ` dpdklab
2024-03-06 18:28 ` dpdklab
2024-03-06 18:35 ` dpdklab
2024-03-06 18:39 ` dpdklab
2024-03-06 18:41 ` dpdklab
2024-03-06 18:42 ` dpdklab
2024-03-06 18:43 ` dpdklab
2024-03-06 18:43 ` dpdklab
2024-03-06 18:44 ` dpdklab
2024-03-06 18:44 ` dpdklab
2024-03-06 18:44 ` dpdklab
2024-03-06 18:44 ` dpdklab
2024-03-06 18:45 ` dpdklab
2024-03-06 18:46 ` dpdklab
2024-03-06 18:46 ` dpdklab
2024-03-06 18:46 ` dpdklab
2024-03-06 18:46 ` dpdklab
2024-03-06 18:52 ` dpdklab
2024-03-06 18:52 ` dpdklab
2024-03-06 18:52 ` dpdklab
2024-03-06 18:53 ` dpdklab
2024-03-06 18:54 ` dpdklab
2024-03-06 18:55 ` dpdklab
2024-03-06 18:57 ` dpdklab
2024-03-06 19:06 ` dpdklab
2024-03-06 19:06 ` dpdklab
2024-03-06 19:07 ` dpdklab
2024-03-06 19:09 ` dpdklab
2024-03-06 19:09 ` dpdklab
2024-03-06 19:11 ` dpdklab
2024-03-06 19:11 ` dpdklab
2024-03-06 19:11 ` dpdklab
2024-03-06 19:13 ` dpdklab
2024-03-06 19:13 ` dpdklab
2024-03-06 19:13 ` dpdklab
2024-03-06 19:14 ` dpdklab
2024-03-06 19:16 ` dpdklab
2024-03-06 19:22 ` dpdklab
2024-03-06 19:23 ` dpdklab
2024-03-06 19:28 ` dpdklab
2024-03-06 19:35 ` dpdklab
2024-03-06 19:45 ` dpdklab
2024-03-06 20:03 ` dpdklab
2024-03-06 20:13 ` dpdklab
2024-03-06 20:15 ` dpdklab
2024-03-06 20:22 ` dpdklab
2024-03-06 20:25 ` dpdklab
2024-03-06 20:29 ` dpdklab
2024-03-06 20:33 ` dpdklab
2024-03-06 20:36 ` dpdklab
2024-03-06 20:45 ` dpdklab
2024-03-06 20:53 ` dpdklab
2024-03-06 21:10 ` dpdklab
2024-03-06 21:16 ` dpdklab
2024-03-06 21:17 ` dpdklab
2024-03-06 22:50 ` dpdklab
2024-03-07  0:38 ` 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=202403061456.426EuZec3233196@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).