From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140171-140172 [v1 2/2] app/testpmd: introduce VXLAN-GBP and VXLAN-GPE fields
Date: Fri, 17 May 2024 15:43:11 +0800 [thread overview]
Message-ID: <202405170743.44H7hBDW412112@localhost.localdomain> (raw)
In-Reply-To: <20240517080735.1787616-3-gavinl@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140172
_Compilation OK_
Submitter: Gavin Li <gavinl@nvidia.com>
Date: Fri, 17 May 2024 11:07:34 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: baa8e2c6b4d7ce289e891b9c96fb3193311c0f01
140171-140172 --> 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
next parent reply other threads:[~2024-05-17 8:11 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240517080735.1787616-3-gavinl@nvidia.com>
2024-05-17 7:43 ` qemudev [this message]
2024-05-17 7:47 ` qemudev
2024-05-17 8:08 ` |WARNING| pw140172 " checkpatch
2024-05-17 9:04 ` |SUCCESS| " 0-day Robot
2024-05-17 18:52 ` |SUCCESS| pw140171-140172 [PATCH] [v1,2/2] app/testpmd: introduce VX dpdklab
2024-05-17 18:52 ` dpdklab
2024-05-17 18:52 ` dpdklab
2024-05-17 18:52 ` dpdklab
2024-05-17 18:54 ` dpdklab
2024-05-17 18:55 ` dpdklab
2024-05-17 18:56 ` dpdklab
2024-05-17 18:57 ` dpdklab
2024-05-17 19:00 ` dpdklab
2024-05-17 19:04 ` dpdklab
2024-05-17 19:04 ` dpdklab
2024-05-17 19:21 ` dpdklab
2024-05-17 19:22 ` dpdklab
2024-05-17 19:22 ` dpdklab
2024-05-17 19:34 ` dpdklab
2024-05-17 19:37 ` dpdklab
2024-05-17 19:41 ` dpdklab
2024-05-17 19:42 ` dpdklab
2024-05-17 19:43 ` dpdklab
2024-05-17 19:44 ` dpdklab
2024-05-17 19:46 ` dpdklab
2024-05-17 19:46 ` dpdklab
2024-05-17 19:47 ` dpdklab
2024-05-17 19:47 ` dpdklab
2024-05-17 19:48 ` dpdklab
2024-05-17 19:48 ` dpdklab
2024-05-17 19:49 ` dpdklab
2024-05-17 19:50 ` dpdklab
2024-05-17 19:51 ` dpdklab
2024-05-17 19:54 ` dpdklab
2024-05-17 19:55 ` |FAILURE| " dpdklab
2024-05-17 19:57 ` dpdklab
2024-05-17 19:58 ` dpdklab
2024-05-17 19:58 ` |SUCCESS| " dpdklab
2024-05-17 19:59 ` dpdklab
2024-05-17 19:59 ` dpdklab
2024-05-17 20:01 ` dpdklab
2024-05-17 20:01 ` |FAILURE| " dpdklab
2024-05-17 20:02 ` |SUCCESS| " dpdklab
2024-05-17 20:04 ` dpdklab
2024-05-17 20:04 ` dpdklab
2024-05-17 20:07 ` |FAILURE| " dpdklab
2024-05-17 20:07 ` dpdklab
2024-05-17 20:08 ` |SUCCESS| " dpdklab
2024-05-17 20:08 ` |FAILURE| " dpdklab
2024-05-17 20:11 ` |SUCCESS| " dpdklab
2024-05-17 20:13 ` dpdklab
2024-05-17 20:13 ` |FAILURE| " dpdklab
2024-05-17 20:16 ` |SUCCESS| " dpdklab
2024-05-17 20:18 ` dpdklab
2024-05-17 20:19 ` |FAILURE| " dpdklab
2024-05-17 20:20 ` |SUCCESS| " dpdklab
2024-05-17 20:20 ` |FAILURE| " dpdklab
2024-05-17 20:21 ` |SUCCESS| " dpdklab
2024-05-17 20:21 ` |FAILURE| " dpdklab
2024-05-17 20:24 ` |SUCCESS| " dpdklab
2024-05-17 20:27 ` dpdklab
2024-05-17 20:28 ` dpdklab
2024-05-17 20:28 ` |FAILURE| " dpdklab
2024-05-17 20:28 ` |SUCCESS| " dpdklab
2024-05-17 20:29 ` |FAILURE| " dpdklab
2024-05-17 20:30 ` |SUCCESS| " dpdklab
2024-05-17 20:31 ` dpdklab
2024-05-17 20:32 ` dpdklab
2024-05-17 20:35 ` dpdklab
2024-05-17 20:36 ` dpdklab
2024-05-17 20:38 ` dpdklab
2024-05-17 20:40 ` dpdklab
2024-05-17 20:41 ` dpdklab
2024-05-17 20:42 ` dpdklab
2024-05-17 20:42 ` dpdklab
2024-05-17 20:43 ` dpdklab
2024-05-17 20:48 ` dpdklab
2024-05-17 20:48 ` dpdklab
2024-05-17 20:48 ` dpdklab
2024-05-17 20:50 ` dpdklab
2024-05-17 20:53 ` dpdklab
2024-05-17 20:53 ` dpdklab
2024-05-17 20:58 ` dpdklab
2024-05-17 20:59 ` dpdklab
2024-05-17 21:02 ` |FAILURE| " dpdklab
2024-05-17 21:06 ` |SUCCESS| " dpdklab
2024-05-17 21:08 ` dpdklab
2024-05-17 21:42 ` dpdklab
2024-05-17 21:50 ` dpdklab
2024-05-17 22:31 ` dpdklab
2024-05-23 6: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=202405170743.44H7hBDW412112@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).