From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139637-139640 [PATCH v1 4/4] dts: refine pre-test setup and teardown steps
Date: Tue, 23 Apr 2024 16:47:40 +0800 [thread overview]
Message-ID: <202404230847.43N8levq939910@localhost.localdomain> (raw)
In-Reply-To: <20240423091252.62924-5-juraj.linkes@pantheon.tech>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139640
_Compilation OK_
Submitter: Juraj Linkeš <juraj.linkes@pantheon.tech>
Date: Tue, 23 Apr 2024 11:12:49 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139637-139640 --> 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-23 9:15 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240423091252.62924-5-juraj.linkes@pantheon.tech>
2024-04-23 8:47 ` qemudev [this message]
2024-04-23 8:51 ` qemudev
2024-04-23 9:14 ` |SUCCESS| pw139640 " checkpatch
2024-04-23 9:55 ` |SUCCESS| pw139637-139640 [PATCH] [v1,4/4] dts: refine pre-test setu dpdklab
2024-04-23 9:56 ` dpdklab
2024-04-23 9:57 ` dpdklab
2024-04-23 9:57 ` dpdklab
2024-04-23 9:57 ` dpdklab
2024-04-23 9:58 ` dpdklab
2024-04-23 9:58 ` dpdklab
2024-04-23 9:59 ` dpdklab
2024-04-23 9:59 ` dpdklab
2024-04-23 9:59 ` dpdklab
2024-04-23 10:01 ` dpdklab
2024-04-23 10:01 ` dpdklab
2024-04-23 10:02 ` dpdklab
2024-04-23 10:07 ` dpdklab
2024-04-23 10:07 ` dpdklab
2024-04-23 10:08 ` dpdklab
2024-04-23 10:08 ` dpdklab
2024-04-23 10:08 ` dpdklab
2024-04-23 10:09 ` |SUCCESS| pw139640 [PATCH v1 4/4] dts: refine pre-test setup and teardown steps 0-day Robot
2024-04-23 10:09 ` |SUCCESS| pw139637-139640 [PATCH] [v1,4/4] dts: refine pre-test setu dpdklab
2024-04-23 10:09 ` dpdklab
2024-04-23 10:09 ` dpdklab
2024-04-23 10:09 ` dpdklab
2024-04-23 10:09 ` dpdklab
2024-04-23 10:09 ` dpdklab
2024-04-23 10:10 ` dpdklab
2024-04-23 10:10 ` dpdklab
2024-04-23 10:10 ` dpdklab
2024-04-23 10:10 ` dpdklab
2024-04-23 10:14 ` dpdklab
2024-04-23 10:14 ` dpdklab
2024-04-23 10:14 ` dpdklab
2024-04-23 10:14 ` dpdklab
2024-04-23 10:14 ` dpdklab
2024-04-23 10:15 ` dpdklab
2024-04-23 10:15 ` dpdklab
2024-04-23 10:15 ` dpdklab
2024-04-23 10:15 ` dpdklab
2024-04-23 10:16 ` dpdklab
2024-04-23 10:16 ` dpdklab
2024-04-23 10:16 ` dpdklab
2024-04-23 10:17 ` dpdklab
2024-04-23 10:17 ` dpdklab
2024-04-23 10:17 ` dpdklab
2024-04-23 10:18 ` dpdklab
2024-04-23 10:18 ` dpdklab
2024-04-23 10:18 ` dpdklab
2024-04-23 10:18 ` dpdklab
2024-04-23 10:18 ` dpdklab
2024-04-23 10:19 ` dpdklab
2024-04-23 10:19 ` dpdklab
2024-04-23 10:19 ` dpdklab
2024-04-23 10:19 ` dpdklab
2024-04-23 10:19 ` dpdklab
2024-04-23 10:20 ` dpdklab
2024-04-23 10:21 ` dpdklab
2024-04-23 10:21 ` dpdklab
2024-04-23 10:22 ` dpdklab
2024-04-23 10:22 ` dpdklab
2024-04-23 10:23 ` dpdklab
2024-04-23 10:23 ` dpdklab
2024-04-23 10:23 ` dpdklab
2024-04-23 10:23 ` dpdklab
2024-04-23 10:24 ` dpdklab
2024-04-23 10:24 ` dpdklab
2024-04-23 10:42 ` dpdklab
2024-04-23 10:42 ` dpdklab
2024-04-23 10:43 ` dpdklab
2024-04-23 10:43 ` dpdklab
2024-04-23 10:43 ` dpdklab
2024-04-23 10:44 ` dpdklab
2024-04-23 10:49 ` dpdklab
2024-04-23 10:49 ` dpdklab
2024-04-23 10:49 ` dpdklab
2024-04-23 10:50 ` dpdklab
2024-04-23 10:50 ` dpdklab
2024-04-23 10:50 ` dpdklab
2024-04-23 10:50 ` dpdklab
2024-04-23 10:51 ` dpdklab
2024-04-23 10:51 ` dpdklab
2024-04-23 10:52 ` dpdklab
2024-04-23 10:56 ` dpdklab
2024-04-23 11:00 ` dpdklab
2024-04-23 11:05 ` dpdklab
2024-04-23 11:06 ` dpdklab
2024-04-23 11:10 ` dpdklab
2024-04-23 11:17 ` dpdklab
2024-04-23 11:35 ` dpdklab
2024-04-23 12:58 ` 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=202404230847.43N8levq939910@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).