From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139828 [PATCH] freebsd: Add support for multiple dpdk instances on FreeBSD
Date: Fri, 3 May 2024 20:22:58 +0800 [thread overview]
Message-ID: <202405031222.443CMwN8812407@localhost.localdomain> (raw)
In-Reply-To: <20240503094615.1427-1-thj@freebsd.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139828
_Compilation OK_
Submitter: Tom Jones <thj@freebsd.org>
Date: Fri, 3 May 2024 09:46:15 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139828 --> 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-03 12:50 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240503094615.1427-1-thj@freebsd.org>
2024-05-03 12:22 ` qemudev [this message]
2024-05-03 12:27 ` qemudev
2024-05-03 12:50 ` checkpatch
2024-05-03 13:39 ` |SUCCESS| pw139828 [PATCH] freebsd: Add support for multiple dpdk in dpdklab
2024-05-03 13:40 ` |FAILURE| " dpdklab
2024-05-03 13:41 ` |SUCCESS| " dpdklab
2024-05-03 13:41 ` dpdklab
2024-05-03 13:42 ` dpdklab
2024-05-03 13:42 ` dpdklab
2024-05-03 13:42 ` dpdklab
2024-05-03 13:43 ` dpdklab
2024-05-03 13:43 ` |FAILURE| " dpdklab
2024-05-03 13:43 ` dpdklab
2024-05-03 13:43 ` |SUCCESS| pw139828 [PATCH] freebsd: Add support for multiple dpdk instances on FreeBSD 0-day Robot
2024-05-03 13:44 ` |SUCCESS| pw139828 [PATCH] freebsd: Add support for multiple dpdk in dpdklab
2024-05-03 13:44 ` dpdklab
2024-05-03 13:44 ` dpdklab
2024-05-03 13:45 ` dpdklab
2024-05-03 13:45 ` |FAILURE| " dpdklab
2024-05-03 13:45 ` dpdklab
2024-05-03 13:45 ` dpdklab
2024-05-03 13:46 ` dpdklab
2024-05-03 13:46 ` |SUCCESS| " dpdklab
2024-05-03 13:47 ` |FAILURE| " dpdklab
2024-05-03 13:47 ` |SUCCESS| " dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:48 ` |FAILURE| " dpdklab
2024-05-03 13:48 ` |SUCCESS| " dpdklab
2024-05-03 13:49 ` dpdklab
2024-05-03 13:50 ` |FAILURE| " dpdklab
2024-05-03 13:50 ` |SUCCESS| " dpdklab
2024-05-03 13:50 ` |FAILURE| " dpdklab
2024-05-03 13:51 ` dpdklab
2024-05-03 13:51 ` |SUCCESS| " dpdklab
2024-05-03 13:51 ` dpdklab
2024-05-03 13:51 ` dpdklab
2024-05-03 13:52 ` dpdklab
2024-05-03 13:52 ` dpdklab
2024-05-03 13:52 ` |FAILURE| " dpdklab
2024-05-03 13:52 ` |SUCCESS| " dpdklab
2024-05-03 13:53 ` dpdklab
2024-05-03 13:53 ` dpdklab
2024-05-03 13:55 ` dpdklab
2024-05-03 13:56 ` dpdklab
2024-05-03 13:56 ` dpdklab
2024-05-03 13:58 ` dpdklab
2024-05-03 13:58 ` dpdklab
2024-05-03 13:58 ` dpdklab
2024-05-03 13:58 ` |FAILURE| " dpdklab
2024-05-03 13:59 ` |SUCCESS| " dpdklab
2024-05-03 13:59 ` dpdklab
2024-05-03 13:59 ` |FAILURE| " dpdklab
2024-05-03 14:00 ` dpdklab
2024-05-03 14:01 ` |SUCCESS| " dpdklab
2024-05-03 14:02 ` dpdklab
2024-05-03 14:03 ` dpdklab
2024-05-03 14:03 ` dpdklab
2024-05-03 14:04 ` |FAILURE| " dpdklab
2024-05-03 14:05 ` |SUCCESS| " dpdklab
2024-05-03 14:06 ` dpdklab
2024-05-03 14:08 ` dpdklab
2024-05-03 14:10 ` dpdklab
2024-05-03 14:13 ` dpdklab
2024-05-03 14:17 ` dpdklab
2024-05-03 14:17 ` dpdklab
2024-05-03 14:18 ` dpdklab
2024-05-03 14:19 ` |FAILURE| " dpdklab
2024-05-03 14:21 ` |SUCCESS| " dpdklab
2024-05-03 14:23 ` dpdklab
2024-05-03 14:23 ` dpdklab
2024-05-03 14:32 ` dpdklab
2024-05-03 15:01 ` dpdklab
2024-05-03 15:06 ` dpdklab
2024-05-03 15:09 ` dpdklab
2024-05-03 15:25 ` dpdklab
2024-05-03 16:01 ` dpdklab
2024-05-03 20:12 ` dpdklab
2024-05-05 6:57 ` dpdklab
2024-05-05 7:16 ` dpdklab
2024-05-05 7:20 ` dpdklab
2024-05-05 7:24 ` dpdklab
2024-05-05 7:28 ` dpdklab
2024-05-06 11:32 ` 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=202405031222.443CMwN8812407@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).