automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw152382-152381 [PATCH v4 3/3] hash_readwrite_autotest: fix printf parameters
Date: Fri, 14 Mar 2025 00:25:16 +0800	[thread overview]
Message-ID: <202503131625.52DGPGA0745023@localhost.localdomain> (raw)
In-Reply-To: <1741884706-21546-4-git-send-email-andremue@linux.microsoft.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/152381

_Compilation OK_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Thu, 13 Mar 2025 09:51:44 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 7d6c28c9199351805e693e9b8f58f60e6f51c2ab

152382-152381 --> 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


       reply	other threads:[~2025-03-13 17:01 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1741884706-21546-4-git-send-email-andremue@linux.microsoft.com>
2025-03-13 16:25 ` qemudev [this message]
2025-03-13 16:29 ` qemudev
2025-03-13 16:53 ` |SUCCESS| pw152381 " checkpatch
2025-03-13 18:03 ` 0-day Robot
2025-03-13 20:04 ` |SUCCESS| pw152382-152381 [PATCH] [v4,3/3] hash_readwrite_autotest: dpdklab
2025-03-13 20:10 ` dpdklab
2025-03-13 20:25 ` dpdklab
2025-03-13 20:25 ` dpdklab
2025-03-13 20:28 ` dpdklab
2025-03-13 20:39 ` dpdklab
2025-03-13 20:48 ` dpdklab
2025-03-13 20:51 ` dpdklab
2025-03-13 20:53 ` dpdklab
2025-03-13 20:53 ` dpdklab
2025-03-13 20:56 ` dpdklab
2025-03-13 21:03 ` dpdklab
2025-03-13 21:03 ` dpdklab
2025-03-13 21:25 ` |PENDING| " dpdklab
2025-03-13 21:28 ` |SUCCESS| " dpdklab
2025-03-13 21:30 ` dpdklab
2025-03-13 21:38 ` |PENDING| " dpdklab
2025-03-13 21:45 ` dpdklab
2025-03-13 21:51 ` |SUCCESS| " dpdklab
2025-03-13 22:03 ` dpdklab
2025-03-13 22:04 ` |PENDING| " dpdklab
2025-03-13 22:35 ` |SUCCESS| " dpdklab
2025-03-13 22:36 ` |PENDING| " dpdklab
2025-03-13 22:38 ` |SUCCESS| " dpdklab
2025-03-13 22:40 ` dpdklab
2025-03-13 22:41 ` dpdklab
2025-03-13 22:43 ` |PENDING| " dpdklab
2025-03-13 22:45 ` |SUCCESS| " dpdklab
2025-03-13 22:51 ` |PENDING| " dpdklab
2025-03-13 23:16 ` |SUCCESS| " dpdklab
2025-03-13 23:22 ` dpdklab
2025-03-13 23:36 ` dpdklab
2025-03-13 23:39 ` dpdklab
2025-03-14  0:24 ` dpdklab
2025-03-14  0:35 ` dpdklab
2025-03-14  0:55 ` dpdklab
2025-03-14  1:03 ` dpdklab
2025-03-14  1:09 ` dpdklab
2025-03-14  3:02 ` 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=202503131625.52DGPGA0745023@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).