From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140547 [PATCH] app/testpmd: fix parsing for connection tracking item
Date: Sun, 2 Jun 2024 17:56:29 +0800 [thread overview]
Message-ID: <202406020956.4529uT4E1832521@localhost.localdomain> (raw)
In-Reply-To: <20240602102328.196672-1-mkashani@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140547
_Compilation OK_
Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Sun, 2 Jun 2024 13:23:26 +0300
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 2dbb63594a9a985e2c8639b57f9fcd1468b9de97
140547 --> 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-06-02 10:25 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240602102328.196672-1-mkashani@nvidia.com>
2024-06-02 9:56 ` qemudev [this message]
2024-06-02 10:00 ` qemudev
2024-06-02 10:24 ` checkpatch
2024-06-02 11:10 ` |SUCCESS| pw140547 [PATCH] app/testpmd: fix parsing for connection t dpdklab
2024-06-02 11:10 ` |FAILURE| " dpdklab
2024-06-02 11:10 ` dpdklab
2024-06-02 11:11 ` |SUCCESS| " dpdklab
2024-06-02 11:11 ` dpdklab
2024-06-02 11:11 ` dpdklab
2024-06-02 11:11 ` dpdklab
2024-06-02 11:11 ` dpdklab
2024-06-02 11:12 ` dpdklab
2024-06-02 11:12 ` |FAILURE| " dpdklab
2024-06-02 11:12 ` dpdklab
2024-06-02 11:12 ` dpdklab
2024-06-02 11:12 ` |SUCCESS| " dpdklab
2024-06-02 11:13 ` dpdklab
2024-06-02 11:13 ` |FAILURE| " dpdklab
2024-06-02 11:13 ` dpdklab
2024-06-02 11:13 ` |SUCCESS| " dpdklab
2024-06-02 11:13 ` dpdklab
2024-06-02 11:13 ` dpdklab
2024-06-02 11:13 ` |FAILURE| " dpdklab
2024-06-02 11:13 ` |SUCCESS| " dpdklab
2024-06-02 11:14 ` dpdklab
2024-06-02 11:14 ` dpdklab
2024-06-02 11:14 ` dpdklab
2024-06-02 11:14 ` dpdklab
2024-06-02 11:14 ` |FAILURE| " dpdklab
2024-06-02 11:14 ` dpdklab
2024-06-02 11:15 ` |SUCCESS| " dpdklab
2024-06-02 11:15 ` |FAILURE| " dpdklab
2024-06-02 11:15 ` dpdklab
2024-06-02 11:15 ` |SUCCESS| " dpdklab
2024-06-02 11:15 ` dpdklab
2024-06-02 11:15 ` dpdklab
2024-06-02 11:15 ` dpdklab
2024-06-02 11:16 ` dpdklab
2024-06-02 11:16 ` dpdklab
2024-06-02 11:16 ` dpdklab
2024-06-02 11:16 ` dpdklab
2024-06-02 11:16 ` dpdklab
2024-06-02 11:17 ` dpdklab
2024-06-02 11:18 ` dpdklab
2024-06-02 11:18 ` dpdklab
2024-06-02 11:19 ` dpdklab
2024-06-02 11:19 ` dpdklab
2024-06-02 11:20 ` dpdklab
2024-06-02 11:20 ` |FAILURE| " dpdklab
2024-06-02 11:20 ` |SUCCESS| " dpdklab
2024-06-02 11:20 ` dpdklab
2024-06-02 11:21 ` dpdklab
2024-06-02 11:21 ` dpdklab
2024-06-02 11:21 ` dpdklab
2024-06-02 11:21 ` dpdklab
2024-06-02 11:22 ` |FAILURE| " dpdklab
2024-06-02 11:22 ` dpdklab
2024-06-02 11:22 ` dpdklab
2024-06-02 11:23 ` |SUCCESS| pw140547 [PATCH] app/testpmd: fix parsing for connection tracking item 0-day Robot
2024-06-02 11:26 ` |SUCCESS| pw140547 [PATCH] app/testpmd: fix parsing for connection t dpdklab
2024-06-02 11:26 ` dpdklab
2024-06-02 11:27 ` |FAILURE| " dpdklab
2024-06-02 11:29 ` dpdklab
2024-06-02 11:29 ` dpdklab
2024-06-02 11:29 ` dpdklab
2024-06-02 11:30 ` |SUCCESS| " dpdklab
2024-06-02 11:30 ` dpdklab
2024-06-02 11:30 ` dpdklab
2024-06-02 11:30 ` |FAILURE| " dpdklab
2024-06-02 11:30 ` |SUCCESS| " dpdklab
2024-06-02 11:32 ` |FAILURE| " dpdklab
2024-06-02 11:32 ` dpdklab
2024-06-02 11:34 ` |SUCCESS| " dpdklab
2024-06-02 11:35 ` |FAILURE| " dpdklab
2024-06-02 11:36 ` |SUCCESS| " dpdklab
2024-06-02 11:36 ` dpdklab
2024-06-02 11:38 ` |FAILURE| " dpdklab
2024-06-02 11:39 ` |SUCCESS| " dpdklab
2024-06-02 11:39 ` |FAILURE| " dpdklab
2024-06-02 11:41 ` |SUCCESS| " dpdklab
2024-06-02 11:41 ` |FAILURE| " dpdklab
2024-06-02 11:41 ` |SUCCESS| " dpdklab
2024-06-02 11:42 ` |FAILURE| " dpdklab
2024-06-02 11:43 ` dpdklab
2024-06-02 11:43 ` dpdklab
2024-06-02 11:46 ` |SUCCESS| " dpdklab
2024-06-02 11:49 ` dpdklab
2024-06-02 11:50 ` dpdklab
2024-06-02 11:50 ` dpdklab
2024-06-02 11:51 ` |FAILURE| " dpdklab
2024-06-02 11:53 ` dpdklab
2024-06-02 11:53 ` dpdklab
2024-06-02 11:57 ` dpdklab
2024-06-02 12:02 ` dpdklab
2024-06-02 12:04 ` dpdklab
2024-06-02 12:10 ` dpdklab
2024-06-02 12:11 ` dpdklab
2024-06-02 12:19 ` dpdklab
2024-06-02 12:23 ` 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=202406020956.4529uT4E1832521@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).