automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw154554-154559 [PATCH v2 6/6] trace: add PMU
Date: Wed, 18 Jun 2025 14:24:18 +0800	[thread overview]
Message-ID: <202506180624.55I6OIB03731539@localhost.localdomain> (raw)
In-Reply-To: <20250618065618.4045910-7-tduszynski@marvell.com>

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

_Compilation OK_

Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Wed, 18 Jun 2025 08:56:13 +0200
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: dbeb8ae8d09387bd525353f4a5aa6ec152cddffa

154554-154559 --> 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-06-18  7:01 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250618065618.4045910-7-tduszynski@marvell.com>
2025-06-18  6:24 ` qemudev [this message]
2025-06-18  6:28 ` qemudev
2025-06-18  6:57 ` |WARNING| pw154559 " checkpatch
2025-06-18  8:04 ` |FAILURE| " 0-day Robot
2025-06-18 11:29 ` |SUCCESS| pw154554-154559 [PATCH] [v2,6/6] " dpdklab
2025-06-18 11:35 ` dpdklab
2025-06-18 11:41 ` dpdklab
2025-06-18 11:44 ` dpdklab
2025-06-18 11:49 ` dpdklab
2025-06-18 12:18 ` dpdklab
2025-06-18 12:20 ` |PENDING| " dpdklab
2025-06-18 12:32 ` |FAILURE| " dpdklab
2025-06-18 12:41 ` |SUCCESS| " dpdklab
2025-06-18 12:42 ` dpdklab
2025-06-18 12:46 ` dpdklab
2025-06-18 12:53 ` |FAILURE| " dpdklab
2025-06-18 13:17 ` dpdklab
2025-06-18 13:23 ` dpdklab
2025-06-18 13:50 ` dpdklab
2025-06-18 14:43 ` |SUCCESS| " dpdklab
2025-06-18 15:38 ` dpdklab
2025-06-18 15:46 ` dpdklab
2025-06-18 15:49 ` dpdklab
2025-06-18 15:50 ` dpdklab
2025-06-18 16:25 ` dpdklab
2025-06-18 16:40 ` dpdklab
2025-06-18 17:14 ` |PENDING| " dpdklab
2025-06-18 17:54 ` |SUCCESS| " dpdklab
2025-06-18 18:20 ` dpdklab
2025-06-18 18:23 ` |FAILURE| " dpdklab
2025-06-18 18:31 ` dpdklab
2025-06-18 18:40 ` dpdklab
2025-06-18 18:43 ` |PENDING| " dpdklab
2025-06-18 18:48 ` |FAILURE| " dpdklab
2025-06-18 19:32 ` dpdklab
2025-06-18 19:34 ` dpdklab
2025-06-18 20:16 ` |SUCCESS| " dpdklab
2025-06-18 20:17 ` dpdklab
2025-06-18 20:17 ` dpdklab
2025-06-18 20:18 ` dpdklab
2025-06-18 20:18 ` dpdklab
2025-06-18 20:19 ` dpdklab
2025-06-18 20:20 ` dpdklab
2025-06-18 20:20 ` dpdklab
2025-06-18 20:32 ` |FAILURE| " dpdklab
2025-06-18 20:49 ` dpdklab
2025-06-18 20:51 ` |SUCCESS| " dpdklab
2025-06-18 21:52 ` |FAILURE| " dpdklab
2025-06-18 23:07 ` |PENDING| " dpdklab
2025-06-18 23:56 ` |FAILURE| " dpdklab
2025-06-19  1:33 ` |SUCCESS| " dpdklab
2025-06-19  1:43 ` dpdklab
2025-06-19  1:48 ` |FAILURE| " dpdklab
2025-06-19  2:53 ` dpdklab
2025-06-19  4:35 ` |SUCCESS| " dpdklab
2025-06-19  4:36 ` dpdklab
2025-06-19  4:39 ` dpdklab
2025-06-19 21:58 ` |FAILURE| " dpdklab
2025-06-19 22:03 ` dpdklab
2025-06-19 23:13 ` dpdklab
2025-06-19 23:40 ` 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=202506180624.55I6OIB03731539@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).