automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139449 [PATCH] devtools: fix version variable not initialized
Date: Wed, 17 Apr 2024 17:09:13 +0800	[thread overview]
Message-ID: <202404170909.43H99Dpn2160388@localhost.localdomain> (raw)
In-Reply-To: <20240417093236.3786106-1-huangdengdui@huawei.com>

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

_Compilation OK_

Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Wed, 17 Apr 2024 17:32:36 +0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139449 --> 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-04-17  9:34 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240417093236.3786106-1-huangdengdui@huawei.com>
2024-04-17  9:09 ` qemudev [this message]
2024-04-17  9:13 ` qemudev
2024-04-17  9:34 ` checkpatch
2024-04-17 10:25 ` 0-day Robot
2024-04-17 15:02 ` |SUCCESS| pw139449 [PATCH] devtools: fix version variable not initia dpdklab
2024-04-17 15:02 ` dpdklab
2024-04-17 15:05 ` dpdklab
2024-04-17 15:08 ` dpdklab
2024-04-17 15:09 ` dpdklab
2024-04-17 15:09 ` dpdklab
2024-04-17 15:09 ` dpdklab
2024-04-17 15:09 ` dpdklab
2024-04-17 15:09 ` dpdklab
2024-04-17 15:35 ` dpdklab
2024-04-17 15:35 ` dpdklab
2024-04-17 15:36 ` dpdklab
2024-04-17 15:36 ` dpdklab
2024-04-17 15:36 ` dpdklab
2024-04-17 15:36 ` dpdklab
2024-04-17 15:37 ` dpdklab
2024-04-17 15:37 ` dpdklab
2024-04-17 15:38 ` dpdklab
2024-04-17 15:38 ` dpdklab
2024-04-17 15:38 ` dpdklab
2024-04-17 15:39 ` dpdklab
2024-04-17 15:39 ` dpdklab
2024-04-17 15:39 ` dpdklab
2024-04-17 15:40 ` dpdklab
2024-04-17 15:40 ` dpdklab
2024-04-17 15:41 ` dpdklab
2024-04-17 15:41 ` dpdklab
2024-04-17 15:41 ` dpdklab
2024-04-17 15:42 ` dpdklab
2024-04-17 15:42 ` dpdklab
2024-04-17 15:42 ` dpdklab
2024-04-17 15:42 ` dpdklab
2024-04-17 15:43 ` dpdklab
2024-04-17 15:44 ` dpdklab
2024-04-17 15:44 ` dpdklab
2024-04-17 15:44 ` dpdklab
2024-04-17 15:45 ` dpdklab
2024-04-17 15:57 ` dpdklab
2024-04-17 15:58 ` dpdklab
2024-04-17 15:59 ` dpdklab
2024-04-17 16:01 ` dpdklab
2024-04-17 16:03 ` dpdklab
2024-04-17 16:03 ` dpdklab
2024-04-17 16:05 ` dpdklab
2024-04-17 16:05 ` dpdklab
2024-04-17 16:05 ` dpdklab
2024-04-17 16:06 ` dpdklab
2024-04-17 16:06 ` dpdklab
2024-04-17 16:07 ` dpdklab
2024-04-17 16:08 ` dpdklab
2024-04-17 16:09 ` dpdklab
2024-04-17 16:09 ` dpdklab
2024-04-17 16:10 ` dpdklab
2024-04-17 16:10 ` dpdklab
2024-04-17 16:10 ` dpdklab
2024-04-17 16:12 ` dpdklab
2024-04-17 16:19 ` dpdklab
2024-04-17 16:20 ` dpdklab
2024-04-17 16:21 ` dpdklab
2024-04-17 16:36 ` dpdklab
2024-04-17 16:37 ` dpdklab
2024-04-17 16:37 ` dpdklab
2024-04-17 16:38 ` dpdklab
2024-04-17 16:38 ` dpdklab
2024-04-17 16:39 ` dpdklab
2024-04-17 16:40 ` dpdklab
2024-04-17 16:41 ` dpdklab
2024-04-17 16:42 ` dpdklab
2024-04-17 16:43 ` dpdklab
2024-04-17 16:43 ` dpdklab
2024-04-17 16:44 ` dpdklab
2024-04-17 16:45 ` dpdklab
2024-04-17 16:45 ` dpdklab
2024-04-17 16:46 ` dpdklab
2024-04-17 16:46 ` dpdklab
2024-04-17 16:47 ` dpdklab
2024-04-17 16:49 ` dpdklab
2024-04-17 16:50 ` dpdklab
2024-04-17 16:50 ` dpdklab
2024-04-17 16:51 ` dpdklab
2024-04-17 16:51 ` dpdklab
2024-04-17 16:53 ` dpdklab
2024-04-17 16:56 ` dpdklab
2024-04-17 16:57 ` dpdklab
2024-04-17 16:58 ` dpdklab
2024-04-17 17:32 ` 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=202404170909.43H99Dpn2160388@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).