automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126417 [PATCH v5] app/testpmd: txonly multiflow port change support
Date: Sat, 22 Apr 2023 07:09:32 +0800	[thread overview]
Message-ID: <202304212309.33LN9Wuv103412@localhost.localdomain> (raw)
In-Reply-To: <20230421232022.342081-1-joshwash@google.com>

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

_Compilation OK_

Submitter: Joshua Washington <joshwash@google.com>
Date: Fri, 21 Apr 2023 16:20:22 -0700
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: f649fd010f2dd3a97e15f2ef106440a79f6c95fb

126417 --> 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-04-21 23:23 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230421232022.342081-1-joshwash@google.com>
2023-04-21 23:09 ` qemudev [this message]
2023-04-21 23:13 ` qemudev
2023-04-21 23:21 ` checkpatch
2023-04-22  0:19 ` 0-day Robot
2023-04-22  0:54 |SUCCESS| pw126417 [PATCH] [v5] " dpdklab
2023-04-22  0:55 dpdklab
2023-04-22  0:57 dpdklab
2023-04-22  1:01 dpdklab
2023-04-22  1:02 dpdklab
2023-04-22  1:03 dpdklab
2023-04-22  1:04 dpdklab
2023-04-22  1:09 dpdklab
2023-04-22  1:09 dpdklab
2023-04-22  1:10 dpdklab
2023-04-22  1:13 dpdklab
2023-04-22  1:17 dpdklab
2023-04-22  1:24 dpdklab
2023-04-22  1:47 dpdklab
2023-04-22  1:57 dpdklab
2023-04-22  2:02 dpdklab
2023-04-22  2:13 dpdklab
2023-04-22  2:15 dpdklab
2023-04-22  2:15 dpdklab
2023-04-22  2:21 dpdklab
2023-04-22  2:23 dpdklab
2023-04-22  2:25 dpdklab
2023-04-22  3:45 dpdklab
2023-04-22  4:17 dpdklab
2023-04-22  4:51 dpdklab
2023-04-25  7:04 dpdklab
2023-04-25  7:04 dpdklab
2023-04-25  7:06 dpdklab
2023-04-25  7:06 dpdklab
2023-04-25  7:09 dpdklab
2023-04-25  7:09 dpdklab
2023-04-25  7:11 dpdklab
2023-04-25  7:11 dpdklab
2023-04-25  7:17 dpdklab
2023-04-25  7:24 dpdklab
2023-04-25  7:27 dpdklab
2023-04-25  7:32 dpdklab
2023-04-25  7:33 dpdklab
2023-04-25  7:33 dpdklab
2023-04-25  7:39 dpdklab
2023-04-25  7:39 dpdklab
2023-04-25  7:40 dpdklab
2023-04-25  7:40 dpdklab
2023-04-25  7:41 dpdklab
2023-04-25  7:42 dpdklab
2023-04-25  7:42 dpdklab
2023-04-25  7:44 dpdklab
2023-04-25  7:44 dpdklab
2023-04-25  7:52 dpdklab
2023-04-25  7:52 dpdklab
2023-04-25  8:04 dpdklab
2023-04-25 13:53 dpdklab
2023-04-25 13:56 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=202304212309.33LN9Wuv103412@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).