From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138997-139010 [PATCH v20 14/14] log: colorize log output
Date: Sun, 31 Mar 2024 00:24:13 +0800 [thread overview]
Message-ID: <202403301624.42UGODq0466212@localhost.localdomain> (raw)
In-Reply-To: <20240330164433.50144-15-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139010
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sat, 30 Mar 2024 09:42:12 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a9778aad62470a38ccbb4e09a2a6bf0cc2e0e36d
138997-139010 --> 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-03-30 16:49 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240330164433.50144-15-stephen@networkplumber.org>
2024-03-30 16:24 ` qemudev [this message]
2024-03-30 16:28 ` qemudev
2024-03-30 16:47 ` |WARNING| pw139010 " checkpatch
2024-03-30 17:28 ` |SUCCESS| pw138997-139010 [PATCH] [v20,14/14] log: colorize log outp dpdklab
2024-03-30 17:28 ` dpdklab
2024-03-30 17:29 ` dpdklab
2024-03-30 17:30 ` dpdklab
2024-03-30 17:31 ` dpdklab
2024-03-30 17:32 ` dpdklab
2024-03-30 17:33 ` dpdklab
2024-03-30 17:34 ` dpdklab
2024-03-30 17:34 ` dpdklab
2024-03-30 17:34 ` dpdklab
2024-03-30 17:35 ` dpdklab
2024-03-30 17:35 ` dpdklab
2024-03-30 17:35 ` dpdklab
2024-03-30 17:36 ` dpdklab
2024-03-30 17:36 ` dpdklab
2024-03-30 17:36 ` dpdklab
2024-03-30 17:36 ` dpdklab
2024-03-30 17:37 ` dpdklab
2024-03-30 17:37 ` dpdklab
2024-03-30 17:38 ` dpdklab
2024-03-30 17:39 ` dpdklab
2024-03-30 17:40 ` dpdklab
2024-03-30 17:40 ` dpdklab
2024-03-30 17:40 ` dpdklab
2024-03-30 17:41 ` dpdklab
2024-03-30 17:41 ` dpdklab
2024-03-30 17:42 ` dpdklab
2024-03-30 17:42 ` dpdklab
2024-03-30 17:43 ` dpdklab
2024-03-30 17:43 ` dpdklab
2024-03-30 17:44 ` dpdklab
2024-03-30 17:44 ` dpdklab
2024-03-30 17:45 ` dpdklab
2024-03-30 17:45 ` dpdklab
2024-03-30 17:45 ` |SUCCESS| pw139010 [PATCH v20 14/14] log: colorize log output 0-day Robot
2024-03-30 17:47 ` |SUCCESS| pw138997-139010 [PATCH] [v20,14/14] log: colorize log outp dpdklab
2024-03-30 17:47 ` dpdklab
2024-03-30 17:47 ` dpdklab
2024-03-30 17:48 ` dpdklab
2024-03-30 17:48 ` dpdklab
2024-03-30 17:49 ` dpdklab
2024-03-30 17:49 ` dpdklab
2024-03-30 17:49 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:50 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:51 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:52 ` dpdklab
2024-03-30 17:53 ` dpdklab
2024-03-30 17:54 ` dpdklab
2024-03-30 17:54 ` dpdklab
2024-03-30 17:55 ` dpdklab
2024-03-30 17:55 ` dpdklab
2024-03-30 17:58 ` dpdklab
2024-03-30 18:00 ` dpdklab
2024-03-30 18:02 ` dpdklab
2024-03-30 18:02 ` dpdklab
2024-03-30 18:03 ` dpdklab
2024-03-30 18:04 ` dpdklab
2024-03-30 18:05 ` dpdklab
2024-03-30 18:06 ` dpdklab
2024-03-30 18:13 ` dpdklab
2024-03-30 18:14 ` dpdklab
2024-03-30 18:15 ` dpdklab
2024-03-30 18:42 ` dpdklab
2024-03-30 18:59 ` dpdklab
2024-03-30 19:10 ` dpdklab
2024-04-03 2:50 ` dpdklab
2024-04-03 2:59 ` dpdklab
2024-04-03 3:14 ` dpdklab
2024-04-03 3:24 ` dpdklab
2024-04-03 3:48 ` 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=202403301624.42UGODq0466212@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).