From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139215-139216 [PATCH v4 2/2] test: add functional test for uuid
Date: Wed, 10 Apr 2024 00:55:50 +0800 [thread overview]
Message-ID: <202404091655.439GtoH6251124@localhost.localdomain> (raw)
In-Reply-To: <20240409170602.541658-3-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139216
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 9 Apr 2024 10:05:02 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139215-139216 --> 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-04-09 17:20 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240409170602.541658-3-stephen@networkplumber.org>
2024-04-09 16:55 ` qemudev [this message]
2024-04-09 17:00 ` qemudev
2024-04-09 17:07 ` |SUCCESS| pw139216 " checkpatch
2024-04-09 17:45 ` |SUCCESS| pw139215-139216 [PATCH] [v4,2/2] test: add functional test dpdklab
2024-04-09 17:46 ` dpdklab
2024-04-09 17:46 ` dpdklab
2024-04-09 17:46 ` dpdklab
2024-04-09 17:47 ` dpdklab
2024-04-09 17:47 ` dpdklab
2024-04-09 17:48 ` dpdklab
2024-04-09 17:48 ` dpdklab
2024-04-09 17:48 ` dpdklab
2024-04-09 17:48 ` dpdklab
2024-04-09 17:48 ` dpdklab
2024-04-09 17:50 ` dpdklab
2024-04-09 17:50 ` dpdklab
2024-04-09 17:51 ` dpdklab
2024-04-09 17:51 ` dpdklab
2024-04-09 17:51 ` dpdklab
2024-04-09 17:52 ` dpdklab
2024-04-09 17:55 ` dpdklab
2024-04-09 17:55 ` dpdklab
2024-04-09 17:56 ` dpdklab
2024-04-09 17:56 ` dpdklab
2024-04-09 17:57 ` dpdklab
2024-04-09 17:57 ` dpdklab
2024-04-09 17:58 ` dpdklab
2024-04-09 17:58 ` dpdklab
2024-04-09 17:59 ` dpdklab
2024-04-09 17:59 ` dpdklab
2024-04-09 18:01 ` dpdklab
2024-04-09 18:01 ` dpdklab
2024-04-09 18:01 ` dpdklab
2024-04-09 18:04 ` |SUCCESS| pw139216 [PATCH v4 2/2] test: add functional test for uuid 0-day Robot
2024-04-09 18:05 ` |SUCCESS| pw139215-139216 [PATCH] [v4,2/2] test: add functional test dpdklab
2024-04-09 18:05 ` dpdklab
2024-04-09 18:10 ` dpdklab
2024-04-09 18:10 ` dpdklab
2024-04-09 18:11 ` dpdklab
2024-04-09 18:12 ` dpdklab
2024-04-09 18:13 ` dpdklab
2024-04-09 18:15 ` dpdklab
2024-04-09 18:15 ` dpdklab
2024-04-09 18:15 ` dpdklab
2024-04-09 18:16 ` dpdklab
2024-04-09 18:16 ` dpdklab
2024-04-09 18:18 ` dpdklab
2024-04-09 18:19 ` dpdklab
2024-04-09 18:19 ` dpdklab
2024-04-09 18:19 ` dpdklab
2024-04-09 18:21 ` dpdklab
2024-04-09 18:22 ` dpdklab
2024-04-09 18:23 ` dpdklab
2024-04-09 18:23 ` dpdklab
2024-04-09 18:26 ` dpdklab
2024-04-09 18:27 ` dpdklab
2024-04-09 18:28 ` dpdklab
2024-04-09 18:30 ` dpdklab
2024-04-09 18:32 ` dpdklab
2024-04-09 18:32 ` dpdklab
2024-04-09 18:32 ` dpdklab
2024-04-09 18:32 ` dpdklab
2024-04-09 18:34 ` dpdklab
2024-04-09 18:35 ` dpdklab
2024-04-09 18:37 ` dpdklab
2024-04-09 18:39 ` dpdklab
2024-04-09 18:39 ` dpdklab
2024-04-09 18:43 ` dpdklab
2024-04-09 18:45 ` dpdklab
2024-04-09 18:45 ` dpdklab
2024-04-09 18:46 ` dpdklab
2024-04-09 18:51 ` dpdklab
2024-04-09 18:52 ` dpdklab
2024-04-09 18:55 ` dpdklab
2024-04-09 18:56 ` dpdklab
2024-04-09 18:56 ` dpdklab
2024-04-09 18:57 ` dpdklab
2024-04-09 19:00 ` dpdklab
2024-04-09 19:01 ` dpdklab
2024-04-09 19:05 ` dpdklab
2024-04-09 19:05 ` dpdklab
2024-04-09 19:06 ` dpdklab
2024-04-09 19:07 ` dpdklab
2024-04-09 19:11 ` dpdklab
2024-04-09 19:18 ` dpdklab
2024-04-09 19:54 ` dpdklab
2024-04-09 20:28 ` dpdklab
2024-04-09 20:39 ` dpdklab
2024-04-09 21:03 ` dpdklab
2024-04-09 21:20 ` 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=202404091655.439GtoH6251124@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).