From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139101-139102 [PATCH v3 2/2] test: add functional test for uuid
Date: Fri, 5 Apr 2024 00:02:22 +0800 [thread overview]
Message-ID: <202404041602.434G2MlT2364346@localhost.localdomain> (raw)
In-Reply-To: <20240404162422.61510-3-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139102
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 4 Apr 2024 09:22:13 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139101-139102 --> 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-04 16:27 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240404162422.61510-3-stephen@networkplumber.org>
2024-04-04 16:02 ` qemudev [this message]
2024-04-04 16:06 ` qemudev
2024-04-04 16:25 ` |SUCCESS| pw139102 " checkpatch
2024-04-04 17:24 ` 0-day Robot
2024-04-04 19:59 ` |SUCCESS| pw139101-139102 [PATCH] [v3,2/2] test: add functional test dpdklab
2024-04-04 20:02 ` dpdklab
2024-04-04 20:03 ` dpdklab
2024-04-04 20:06 ` dpdklab
2024-04-04 20:06 ` dpdklab
2024-04-04 20:12 ` dpdklab
2024-04-04 20:22 ` dpdklab
2024-04-04 20:37 ` dpdklab
2024-04-04 20:52 ` dpdklab
2024-04-04 20:52 ` dpdklab
2024-04-04 20:53 ` dpdklab
2024-04-04 20:53 ` dpdklab
2024-04-04 20:53 ` dpdklab
2024-04-04 20:54 ` dpdklab
2024-04-04 20:54 ` dpdklab
2024-04-04 20:55 ` dpdklab
2024-04-04 20:55 ` dpdklab
2024-04-04 20:56 ` dpdklab
2024-04-04 20:56 ` dpdklab
2024-04-04 20:57 ` dpdklab
2024-04-04 20:57 ` dpdklab
2024-04-04 20:58 ` dpdklab
2024-04-04 20:58 ` dpdklab
2024-04-04 20:58 ` dpdklab
2024-04-04 20:59 ` dpdklab
2024-04-04 21:00 ` dpdklab
2024-04-04 21:00 ` dpdklab
2024-04-04 21:01 ` dpdklab
2024-04-04 21:06 ` dpdklab
2024-04-04 21:07 ` dpdklab
2024-04-04 21:07 ` dpdklab
2024-04-04 21:09 ` dpdklab
2024-04-04 21:10 ` dpdklab
2024-04-04 21:13 ` dpdklab
2024-04-04 21:13 ` dpdklab
2024-04-04 21:15 ` dpdklab
2024-04-04 21:16 ` dpdklab
2024-04-04 21:20 ` dpdklab
2024-04-04 21:21 ` dpdklab
2024-04-04 21:21 ` dpdklab
2024-04-04 21:22 ` dpdklab
2024-04-04 21:22 ` dpdklab
2024-04-04 21:22 ` dpdklab
2024-04-04 21:23 ` dpdklab
2024-04-04 21:24 ` dpdklab
2024-04-04 21:25 ` dpdklab
2024-04-04 21:25 ` dpdklab
2024-04-04 21:27 ` dpdklab
2024-04-04 21:36 ` dpdklab
2024-04-04 21:36 ` dpdklab
2024-04-04 21:38 ` dpdklab
2024-04-04 21:40 ` dpdklab
2024-04-04 21:51 ` dpdklab
2024-04-04 21:52 ` dpdklab
2024-04-04 21:53 ` dpdklab
2024-04-04 21:53 ` dpdklab
2024-04-04 21:55 ` dpdklab
2024-04-04 21:56 ` dpdklab
2024-04-04 21:59 ` dpdklab
2024-04-04 22:07 ` dpdklab
2024-04-04 22:08 ` dpdklab
2024-04-04 22:16 ` dpdklab
2024-04-04 22:22 ` dpdklab
2024-04-04 22:25 ` dpdklab
2024-04-04 22:30 ` dpdklab
2024-04-04 22:32 ` dpdklab
2024-04-04 22:35 ` dpdklab
2024-04-04 22:36 ` dpdklab
2024-04-04 22:38 ` dpdklab
2024-04-04 22:39 ` dpdklab
2024-04-04 22:39 ` dpdklab
2024-04-04 22:50 ` dpdklab
2024-04-04 22:50 ` dpdklab
2024-04-04 22:52 ` dpdklab
2024-04-04 22:56 ` dpdklab
2024-04-04 23:09 ` dpdklab
2024-04-04 23:10 ` dpdklab
2024-04-04 23:25 ` dpdklab
2024-04-04 23:29 ` dpdklab
2024-04-04 23:41 ` dpdklab
2024-04-04 23:46 ` dpdklab
2024-04-04 23:48 ` dpdklab
2024-04-04 23:52 ` dpdklab
2024-04-04 23:52 ` dpdklab
2024-04-04 23:56 ` dpdklab
2024-04-04 23:57 ` dpdklab
2024-04-05 0:02 ` dpdklab
2024-04-05 0:16 ` 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=202404041602.434G2MlT2364346@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).