From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138434 [PATCH] devtools: download scripts from linux if not found
Date: Fri, 15 Mar 2024 21:51:47 +0800 [thread overview]
Message-ID: <202403151351.42FDpllX1880079@localhost.localdomain> (raw)
In-Reply-To: <20240315141441.259594-2-rjarry@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138434
_Compilation OK_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Fri, 15 Mar 2024 15:14:42 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 90a91f8761af9f99243e1ca35082fcf05ff7a9b2
138434 --> 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-15 14:16 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240315141441.259594-2-rjarry@redhat.com>
2024-03-15 13:51 ` qemudev [this message]
2024-03-15 13:56 ` qemudev
2024-03-15 14:16 ` |WARNING| " checkpatch
2024-03-15 14:59 ` |SUCCESS| pw138434 [PATCH] devtools: download scripts from linux if dpdklab
2024-03-15 15:00 ` dpdklab
2024-03-15 15:01 ` dpdklab
2024-03-15 15:02 ` dpdklab
2024-03-15 15:02 ` dpdklab
2024-03-15 15:03 ` dpdklab
2024-03-15 15:03 ` |SUCCESS| pw138434 [PATCH] devtools: download scripts from linux if not found 0-day Robot
2024-03-15 15:03 ` |SUCCESS| pw138434 [PATCH] devtools: download scripts from linux if dpdklab
2024-03-15 15:03 ` dpdklab
2024-03-15 15:04 ` dpdklab
2024-03-15 15:04 ` dpdklab
2024-03-15 15:05 ` dpdklab
2024-03-15 15:05 ` dpdklab
2024-03-15 15:06 ` dpdklab
2024-03-15 15:06 ` dpdklab
2024-03-15 15:07 ` dpdklab
2024-03-15 15:07 ` dpdklab
2024-03-15 15:08 ` dpdklab
2024-03-15 15:08 ` dpdklab
2024-03-15 15:09 ` dpdklab
2024-03-15 15:09 ` dpdklab
2024-03-15 15:09 ` dpdklab
2024-03-15 15:09 ` dpdklab
2024-03-15 15:10 ` dpdklab
2024-03-15 15:10 ` dpdklab
2024-03-15 15:10 ` dpdklab
2024-03-15 15:10 ` dpdklab
2024-03-15 15:11 ` dpdklab
2024-03-15 15:11 ` dpdklab
2024-03-15 15:11 ` dpdklab
2024-03-15 15:12 ` dpdklab
2024-03-15 15:12 ` dpdklab
2024-03-15 15:12 ` dpdklab
2024-03-15 15:12 ` dpdklab
2024-03-15 15:12 ` dpdklab
2024-03-15 15:13 ` dpdklab
2024-03-15 15:13 ` dpdklab
2024-03-15 15:13 ` dpdklab
2024-03-15 15:14 ` dpdklab
2024-03-15 15:14 ` dpdklab
2024-03-15 15:14 ` dpdklab
2024-03-15 15:14 ` dpdklab
2024-03-15 15:14 ` dpdklab
2024-03-15 15:14 ` dpdklab
2024-03-15 15:14 ` dpdklab
2024-03-15 15:14 ` dpdklab
2024-03-15 15:14 ` dpdklab
2024-03-15 15:14 ` dpdklab
2024-03-15 15:15 ` dpdklab
2024-03-15 15:15 ` dpdklab
2024-03-15 15:15 ` dpdklab
2024-03-15 15:15 ` dpdklab
2024-03-15 15:15 ` dpdklab
2024-03-15 15:15 ` dpdklab
2024-03-15 15:15 ` dpdklab
2024-03-15 15:16 ` dpdklab
2024-03-15 15:16 ` dpdklab
2024-03-15 15:16 ` dpdklab
2024-03-15 15:16 ` dpdklab
2024-03-15 15:17 ` dpdklab
2024-03-15 15:17 ` dpdklab
2024-03-15 15:18 ` dpdklab
2024-03-15 15:19 ` dpdklab
2024-03-15 15:21 ` dpdklab
2024-03-15 15:28 ` dpdklab
2024-03-15 15:28 ` dpdklab
2024-03-15 15:29 ` dpdklab
2024-03-15 15:29 ` dpdklab
2024-03-15 15:29 ` dpdklab
2024-03-15 15:57 ` dpdklab
2024-03-15 16:02 ` dpdklab
2024-03-15 16:03 ` dpdklab
2024-03-15 16:25 ` dpdklab
2024-03-19 8:09 ` dpdklab
2024-03-19 8:44 ` 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=202403151351.42FDpllX1880079@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).