From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw152831 [RFC 1/1] build: support ThreadSanitizer
Date: Tue, 8 Apr 2025 20:50:30 +0800 [thread overview]
Message-ID: <202504081250.538CoUAL755155@localhost.localdomain> (raw)
In-Reply-To: <20250408130556.1054041-2-huangdengdui@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/152831
_Compilation OK_
Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Tue, 8 Apr 2025 21:05:56 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 8ee74a69abcf48563f05adeafecd298bb03477a8
152831 --> 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:[~2025-04-08 13:26 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250408130556.1054041-2-huangdengdui@huawei.com>
2025-04-08 12:50 ` qemudev [this message]
2025-04-08 12:55 ` qemudev
2025-04-08 13:06 ` checkpatch
2025-04-08 14:23 ` 0-day Robot
2025-04-08 15:15 ` |SUCCESS| pw152831 [PATCH] [RFC,1/1] " dpdklab
2025-04-08 15:16 ` |PENDING| " dpdklab
2025-04-08 15:28 ` |SUCCESS| " dpdklab
2025-04-08 15:31 ` dpdklab
2025-04-08 15:33 ` dpdklab
2025-04-08 15:37 ` dpdklab
2025-04-08 15:40 ` dpdklab
2025-04-08 15:41 ` dpdklab
2025-04-08 15:41 ` dpdklab
2025-04-08 15:48 ` dpdklab
2025-04-08 15:49 ` dpdklab
2025-04-08 15:51 ` |PENDING| " dpdklab
2025-04-08 15:52 ` dpdklab
2025-04-08 15:57 ` |SUCCESS| " dpdklab
2025-04-08 15:57 ` dpdklab
2025-04-08 16:00 ` |PENDING| " dpdklab
2025-04-08 16:03 ` |SUCCESS| " dpdklab
2025-04-08 16:05 ` dpdklab
2025-04-08 16:10 ` dpdklab
2025-04-08 16:15 ` dpdklab
2025-04-08 16:15 ` dpdklab
2025-04-08 16:21 ` dpdklab
2025-04-08 16:23 ` |FAILURE| " dpdklab
2025-04-08 16:25 ` |SUCCESS| " dpdklab
2025-04-08 16:28 ` dpdklab
2025-04-08 16:32 ` |PENDING| " dpdklab
2025-04-08 16:35 ` |SUCCESS| " dpdklab
2025-04-08 16:36 ` dpdklab
2025-04-08 16:37 ` dpdklab
2025-04-08 16:51 ` dpdklab
2025-04-08 16:55 ` |PENDING| " dpdklab
2025-04-08 16:56 ` |SUCCESS| " dpdklab
2025-04-08 17:02 ` dpdklab
2025-04-08 17:15 ` dpdklab
2025-04-08 17:16 ` dpdklab
2025-04-08 17:19 ` dpdklab
2025-04-08 17:35 ` dpdklab
2025-04-08 17:40 ` |PENDING| " dpdklab
2025-04-08 17:55 ` |SUCCESS| " dpdklab
2025-04-08 18:07 ` dpdklab
2025-04-08 18:08 ` dpdklab
2025-04-08 18:15 ` dpdklab
2025-04-08 18:18 ` dpdklab
2025-04-08 18:23 ` dpdklab
2025-04-08 18:54 ` dpdklab
2025-04-08 18:56 ` 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=202504081250.538CoUAL755155@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).