automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122740-122742 [PATCH v4 3/3] app/testpmd: add IPv6 routing extension header in raw encap
Date: Tue, 31 Jan 2023 17:32:04 +0800	[thread overview]
Message-ID: <202301310932.30V9W4Iu3562800@localhost.localdomain> (raw)
In-Reply-To: <20230131093657.2240006-4-rongweil@nvidia.com>

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

_Compilation OK_

Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Tue, 31 Jan 2023 11:36:55 +0200
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 02ae4c526efd88d858d8f04fc0ef339238ef5d99

122740-122742 --> 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-01-31  9:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230131093657.2240006-4-rongweil@nvidia.com>
2023-01-31  9:32 ` qemudev [this message]
2023-01-31  9:36 ` qemudev
2023-01-31  9:39 ` |SUCCESS| pw122742 " checkpatch
2023-01-31 10:32 ` 0-day Robot
2023-01-31 19:15 |SUCCESS| pw122740-122742 [PATCH] [v4, " dpdklab
2023-01-31 19:44 dpdklab
2023-01-31 20:00 dpdklab
2023-01-31 20:06 dpdklab
2023-01-31 21:35 dpdklab
2023-01-31 21:42 dpdklab
2023-01-31 22:17 dpdklab
2023-01-31 22:24 dpdklab
2023-02-01  0:08 dpdklab
2023-02-01  9:45 dpdklab
2023-02-01 10:47 dpdklab
2023-02-01 10:47 dpdklab
2023-02-01 10:47 dpdklab
2023-02-01 10:47 dpdklab
2023-02-01 10:47 dpdklab
2023-02-01 10:48 dpdklab
2023-02-01 18:26 dpdklab
2023-02-01 19:06 dpdklab
2023-02-01 20:18 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=202301310932.30V9W4Iu3562800@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).