From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138202-138203 [PATCH 3/3] app/testpmd: support setting lanes
Date: Tue, 12 Mar 2024 15:32:07 +0800 [thread overview]
Message-ID: <202403120732.42C7W76t2984884@localhost.localdomain> (raw)
In-Reply-To: <20240312075238.3319480-4-huangdengdui@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138203
_Compilation OK_
Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Tue, 12 Mar 2024 15:52:36 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: e3faaed01e14ffdfe8f4190030540ed874184b55
138202-138203 --> 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-03-12 7:56 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240312075238.3319480-4-huangdengdui@huawei.com>
2024-03-12 7:32 ` qemudev [this message]
2024-03-12 7:36 ` |FAILURE| " qemudev
2024-03-12 7:53 ` |SUCCESS| pw138203 " checkpatch
2024-03-12 8:42 ` |FAILURE| " 0-day Robot
2024-03-12 9:50 ` |SUCCESS| pw138202-138203 [PATCH] [3/3] app/testpmd: support setting dpdklab
2024-03-12 9:59 ` dpdklab
2024-03-12 10:12 ` dpdklab
2024-03-12 10:12 ` dpdklab
2024-03-12 10:13 ` dpdklab
2024-03-12 10:13 ` dpdklab
2024-03-12 10:14 ` dpdklab
2024-03-12 10:21 ` dpdklab
2024-03-12 10:22 ` dpdklab
2024-03-12 10:22 ` dpdklab
2024-03-12 10:23 ` dpdklab
2024-03-12 10:23 ` |WARNING| " dpdklab
2024-03-12 10:23 ` |SUCCESS| " dpdklab
2024-03-12 10:23 ` |FAILURE| " dpdklab
2024-03-12 10:23 ` |WARNING| " dpdklab
2024-03-12 10:23 ` dpdklab
2024-03-12 10:24 ` |SUCCESS| " dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:26 ` dpdklab
2024-03-12 10:29 ` |WARNING| " dpdklab
2024-03-12 10:30 ` |SUCCESS| " dpdklab
2024-03-12 10:31 ` |WARNING| " dpdklab
2024-03-12 10:31 ` dpdklab
2024-03-12 10:32 ` |SUCCESS| " dpdklab
2024-03-12 10:32 ` dpdklab
2024-03-12 10:33 ` dpdklab
2024-03-12 10:33 ` |WARNING| " dpdklab
2024-03-12 10:34 ` dpdklab
2024-03-12 10:34 ` |SUCCESS| " dpdklab
2024-03-12 10:34 ` |FAILURE| " dpdklab
2024-03-12 10:35 ` |SUCCESS| " dpdklab
2024-03-12 10:35 ` |WARNING| " dpdklab
2024-03-12 10:35 ` |SUCCESS| " dpdklab
2024-03-12 10:36 ` dpdklab
2024-03-12 10:36 ` |FAILURE| " dpdklab
2024-03-12 10:36 ` |WARNING| " dpdklab
2024-03-12 10:37 ` |FAILURE| " dpdklab
2024-03-12 10:37 ` |SUCCESS| " dpdklab
2024-03-12 10:37 ` dpdklab
2024-03-12 10:37 ` |FAILURE| " dpdklab
2024-03-12 10:37 ` |SUCCESS| " dpdklab
2024-03-12 10:41 ` |FAILURE| " dpdklab
2024-03-12 10:41 ` dpdklab
2024-03-12 10:41 ` dpdklab
2024-03-12 10:43 ` dpdklab
2024-03-12 10:44 ` dpdklab
2024-03-12 10:50 ` dpdklab
2024-03-12 10:53 ` dpdklab
2024-03-12 10:58 ` dpdklab
2024-03-12 10:58 ` dpdklab
2024-03-12 10:58 ` |SUCCESS| " dpdklab
2024-03-12 10:59 ` |FAILURE| " dpdklab
2024-03-12 11:00 ` |SUCCESS| " dpdklab
2024-03-12 11:01 ` |FAILURE| " dpdklab
2024-03-12 11:06 ` dpdklab
2024-03-12 11:07 ` |SUCCESS| " dpdklab
2024-03-12 11:08 ` |FAILURE| " dpdklab
2024-03-12 11:08 ` |SUCCESS| " dpdklab
2024-03-12 11:09 ` |FAILURE| " dpdklab
2024-03-12 11:09 ` |SUCCESS| " dpdklab
2024-03-12 11:11 ` dpdklab
2024-03-12 11:15 ` |FAILURE| " dpdklab
2024-03-12 11:18 ` |SUCCESS| " dpdklab
2024-03-12 12:10 ` dpdklab
2024-03-12 12:24 ` dpdklab
2024-03-12 13:11 ` dpdklab
2024-03-15 20:07 ` dpdklab
2024-03-15 20:36 ` 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=202403120732.42C7W76t2984884@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).