automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw152261 [PATCH] hash_multiwriter_autotest: fix printf parameters
Date: Thu, 6 Mar 2025 03:11:19 +0800	[thread overview]
Message-ID: <202503051911.525JBJPq4158955@localhost.localdomain> (raw)
In-Reply-To: <1741203955-15203-1-git-send-email-andremue@linux.microsoft.com>

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

_Compilation OK_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Wed,  5 Mar 2025 11:45:55 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 7fa30bca91de033016b9b1b34dbda20ce347a298

152261 --> 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-05 19:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1741203955-15203-1-git-send-email-andremue@linux.microsoft.com>
2025-03-05 19:11 ` qemudev [this message]
2025-03-05 19:15 ` qemudev
2025-03-05 19:46 ` checkpatch
2025-03-05 21:02 ` |SUCCESS| pw152261 [PATCH] hash_multiwriter_autotest: fix printf par dpdklab
2025-03-05 21:04 ` |SUCCESS| pw152261 [PATCH] hash_multiwriter_autotest: fix printf parameters 0-day Robot
2025-03-05 21:11 ` |SUCCESS| pw152261 [PATCH] hash_multiwriter_autotest: fix printf par dpdklab
2025-03-05 21:14 ` |FAILURE| " dpdklab
2025-03-05 21:25 ` |SUCCESS| " dpdklab
2025-03-05 21:26 ` |FAILURE| " dpdklab
2025-03-05 21:37 ` dpdklab
2025-03-05 22:13 ` dpdklab
2025-03-05 22:16 ` |SUCCESS| " dpdklab
2025-03-05 22:29 ` dpdklab
2025-03-05 22:32 ` |PENDING| " dpdklab
2025-03-05 22:35 ` dpdklab
2025-03-05 22:35 ` |SUCCESS| " dpdklab
2025-03-05 23:12 ` |PENDING| " dpdklab
2025-03-05 23:20 ` |SUCCESS| " dpdklab
2025-03-05 23:22 ` |PENDING| " dpdklab
2025-03-06  0:41 ` |SUCCESS| " dpdklab
2025-03-06  0:50 ` dpdklab
2025-03-06  0:58 ` dpdklab
2025-03-06  0:59 ` dpdklab
2025-03-06  1:18 ` dpdklab
2025-03-06  4:28 ` dpdklab
2025-03-06  5:08 ` dpdklab
2025-03-06  6:44 ` dpdklab
2025-03-06  6:46 ` dpdklab
2025-03-06  6:59 ` dpdklab
2025-03-06  7:55 ` dpdklab
2025-03-06  8:06 ` dpdklab
2025-03-06  8:18 ` dpdklab
2025-03-06  9:14 ` dpdklab
2025-03-06  9:26 ` 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=202503051911.525JBJPq4158955@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).