automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144433-144438 [PATCH v2 7/7] ethdev: add trace points to flow insertion by index
Date: Thu, 26 Sep 2024 01:41:15 +0800	[thread overview]
Message-ID: <202409251741.48PHfFWx2200876@localhost.localdomain> (raw)
In-Reply-To: <20240925180532.3958656-8-akozyrev@nvidia.com>

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

_Compilation OK_

Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Wed, 25 Sep 2024 21:05:26 +0300
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 177572d1fa5aad1f3c13206b6fae0195d7e55934

144433-144438 --> 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:[~2024-09-25 18:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240925180532.3958656-8-akozyrev@nvidia.com>
2024-09-25 17:41 ` qemudev [this message]
2024-09-25 17:45 ` qemudev
2024-09-25 18:09 ` |SUCCESS| pw144438 " checkpatch
2024-09-26  4:40 ` |SUCCESS| pw144433-144438 [PATCH] [v2,7/7] ethdev: add trace points dpdklab
2024-09-26  4:49 ` dpdklab
2024-09-26  4:50 ` dpdklab
2024-09-26  4:51 ` dpdklab
2024-09-26  4:52 ` dpdklab
2024-09-26  4:57 ` dpdklab
2024-09-26  5:15 ` dpdklab
2024-09-26  5:36 ` dpdklab
2024-09-26  6:27 ` dpdklab
2024-09-26  6:28 ` dpdklab
2024-09-26  6:54 ` |PENDING| " dpdklab
2024-09-26  6:54 ` dpdklab
2024-09-26  8:14 ` |SUCCESS| " dpdklab
2024-09-26  8:36 ` dpdklab
2024-09-26  8:53 ` dpdklab
2024-09-26  8:55 ` dpdklab
2024-09-26  9:50 ` dpdklab
2024-09-26 11:24 ` dpdklab
2024-09-26 12:36 ` dpdklab
2024-09-26 13:04 ` dpdklab
2024-09-26 13:19 ` 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=202409251741.48PHfFWx2200876@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).