automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124914-124922 [PATCH v5 9/9] table: enable build on Windows
Date: Fri, 10 Mar 2023 05:21:11 +0800	[thread overview]
Message-ID: <202303092121.329LLBRn2761862@localhost.localdomain> (raw)
In-Reply-To: <20230309213128.34146-10-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu,  9 Mar 2023 13:31:20 -0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 0e3549a75d53a5f37e0ca521c6603e55a9bdbf79

124914-124922 --> 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-03-09 21:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230309213128.34146-10-stephen@networkplumber.org>
2023-03-09 21:21 ` qemudev [this message]
2023-03-09 21:25 ` qemudev
2023-03-09 21:33 ` |SUCCESS| pw124922 " checkpatch
2023-03-09 23:59 ` 0-day Robot
2023-03-10  2:55 |SUCCESS| pw124914-124922 [PATCH] [v5, " dpdklab
2023-03-10  2:55 dpdklab
2023-03-10  2:56 dpdklab
2023-03-10  2:57 dpdklab
2023-03-10  3:07 dpdklab
2023-03-10  3:08 dpdklab
2023-03-10  3:11 dpdklab
2023-03-10  3:13 dpdklab
2023-03-10  3:16 dpdklab
2023-03-10  3:17 dpdklab
2023-03-10  3:20 dpdklab
2023-03-10  3:22 dpdklab
2023-03-10  3:26 dpdklab
2023-03-10  3:34 dpdklab
2023-03-10 11:06 dpdklab
2023-03-10 18:03 dpdklab
2023-03-10 21:43 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=202303092121.329LLBRn2761862@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).