From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140655-140668 [PATCH v21 14/14] log: colorize log output
Date: Tue, 4 Jun 2024 08:43:37 +0800 [thread overview]
Message-ID: <202406040043.4540hbxc2198625@localhost.localdomain> (raw)
In-Reply-To: <20240604004731.6654-15-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140668
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 3 Jun 2024 17:44:49 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 76cef1af8bdaeaf67a5c4ca5df3f221df994dc46
140655-140668 --> 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-04 1:12 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240604004731.6654-15-stephen@networkplumber.org>
2024-06-04 0:43 ` qemudev [this message]
2024-06-04 0:48 ` qemudev
2024-06-04 0:51 ` |WARNING| pw140668 " checkpatch
2024-06-04 1:31 ` |SUCCESS| pw140655-140668 [PATCH] [v21,14/14] log: colorize log outp dpdklab
2024-06-04 1:31 ` dpdklab
2024-06-04 1:31 ` dpdklab
2024-06-04 1:32 ` dpdklab
2024-06-04 1:32 ` dpdklab
2024-06-04 1:32 ` dpdklab
2024-06-04 1:32 ` dpdklab
2024-06-04 1:32 ` dpdklab
2024-06-04 1:33 ` dpdklab
2024-06-04 1:33 ` dpdklab
2024-06-04 1:33 ` dpdklab
2024-06-04 1:34 ` dpdklab
2024-06-04 1:34 ` dpdklab
2024-06-04 1:34 ` dpdklab
2024-06-04 1:34 ` dpdklab
2024-06-04 1:34 ` dpdklab
2024-06-04 1:35 ` dpdklab
2024-06-04 1:36 ` dpdklab
2024-06-04 1:36 ` dpdklab
2024-06-04 1:37 ` dpdklab
2024-06-04 1:37 ` dpdklab
2024-06-04 1:37 ` dpdklab
2024-06-04 1:37 ` dpdklab
2024-06-04 1:42 ` dpdklab
2024-06-04 1:42 ` dpdklab
2024-06-04 1:43 ` dpdklab
2024-06-04 1:43 ` dpdklab
2024-06-04 1:44 ` dpdklab
2024-06-04 1:44 ` |SUCCESS| pw140668 [PATCH v21 14/14] log: colorize log output 0-day Robot
2024-06-04 1:44 ` |SUCCESS| pw140655-140668 [PATCH] [v21,14/14] log: colorize log outp dpdklab
2024-06-04 1:44 ` dpdklab
2024-06-04 1:45 ` dpdklab
2024-06-04 1:45 ` dpdklab
2024-06-04 1:46 ` dpdklab
2024-06-04 1:46 ` dpdklab
2024-06-04 1:47 ` dpdklab
2024-06-04 1:48 ` dpdklab
2024-06-04 1:49 ` dpdklab
2024-06-04 1:49 ` dpdklab
2024-06-04 1:50 ` dpdklab
2024-06-04 1:50 ` dpdklab
2024-06-04 1:51 ` dpdklab
2024-06-04 1:52 ` dpdklab
2024-06-04 1:52 ` dpdklab
2024-06-04 1:53 ` dpdklab
2024-06-04 1:54 ` dpdklab
2024-06-04 1:55 ` dpdklab
2024-06-04 1:55 ` dpdklab
2024-06-04 1:55 ` dpdklab
2024-06-04 1:56 ` dpdklab
2024-06-04 1:56 ` dpdklab
2024-06-04 1:57 ` dpdklab
2024-06-04 1:58 ` dpdklab
2024-06-04 1:59 ` dpdklab
2024-06-04 2:01 ` dpdklab
2024-06-04 2:03 ` dpdklab
2024-06-04 2:03 ` dpdklab
2024-06-04 2:03 ` dpdklab
2024-06-04 2:05 ` dpdklab
2024-06-04 2:05 ` dpdklab
2024-06-04 2:06 ` dpdklab
2024-06-04 2:06 ` dpdklab
2024-06-04 2:06 ` dpdklab
2024-06-04 2:07 ` dpdklab
2024-06-04 2:07 ` dpdklab
2024-06-04 2:08 ` dpdklab
2024-06-04 2:09 ` dpdklab
2024-06-04 2:10 ` dpdklab
2024-06-04 2:10 ` dpdklab
2024-06-04 2:10 ` dpdklab
2024-06-04 2:10 ` dpdklab
2024-06-04 2:11 ` dpdklab
2024-06-04 2:11 ` dpdklab
2024-06-04 2:12 ` dpdklab
2024-06-04 2:13 ` dpdklab
2024-06-04 2:13 ` dpdklab
2024-06-04 2:13 ` dpdklab
2024-06-04 2:14 ` dpdklab
2024-06-04 2:16 ` dpdklab
2024-06-04 2:16 ` dpdklab
2024-06-04 2:16 ` dpdklab
2024-06-04 2:16 ` dpdklab
2024-06-04 2:22 ` dpdklab
2024-06-04 2:22 ` dpdklab
2024-06-04 2:22 ` dpdklab
2024-06-04 2:23 ` dpdklab
2024-06-04 2:29 ` dpdklab
2024-06-04 2:30 ` dpdklab
2024-06-04 2:34 ` dpdklab
2024-06-04 2:37 ` dpdklab
2024-06-04 2:38 ` dpdklab
2024-06-04 2:47 ` dpdklab
2024-06-04 2:57 ` dpdklab
2024-06-04 3:19 ` dpdklab
2024-06-04 5:03 ` dpdklab
2024-06-04 5:06 ` 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=202406040043.4540hbxc2198625@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).