From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw150197 [PATCH] test: improve resiliency of malloc autotest
Date: Fri, 17 Jan 2025 20:38:29 +0800 [thread overview]
Message-ID: <202501171238.50HCcTnl1689503@localhost.localdomain> (raw)
In-Reply-To: <20250117125912.985475-1-bruce.richardson@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/150197
_Compilation OK_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Fri, 17 Jan 2025 12:59:12 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 06e2856620a70000b2a28f0ea715fc247b85fd8d
150197 --> 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-01-17 13:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250117125912.985475-1-bruce.richardson@intel.com>
2025-01-17 12:38 ` qemudev [this message]
2025-01-17 12:43 ` |FAILURE| " qemudev
2025-01-17 13:00 ` |SUCCESS| " checkpatch
2025-01-17 14:05 ` |FAILURE| " 0-day Robot
2025-01-17 17:11 ` |SUCCESS| pw150197 [PATCH] test: improve resiliency of malloc autote dpdklab
2025-01-17 17:12 ` dpdklab
2025-01-17 17:16 ` dpdklab
2025-01-17 17:22 ` dpdklab
2025-01-17 17:29 ` dpdklab
2025-01-17 17:32 ` dpdklab
2025-01-17 17:37 ` dpdklab
2025-01-17 17:40 ` |PENDING| " dpdklab
2025-01-17 18:01 ` |SUCCESS| " dpdklab
2025-01-17 18:07 ` dpdklab
2025-01-17 18:16 ` dpdklab
2025-01-17 18:33 ` dpdklab
2025-01-17 19:56 ` |WARNING| " dpdklab
2025-01-17 19:57 ` dpdklab
2025-01-17 20:29 ` |SUCCESS| " dpdklab
2025-01-17 20:34 ` dpdklab
2025-01-17 22:27 ` |WARNING| " 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=202501171238.50HCcTnl1689503@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).