automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144269 [PATCH v3] ethdev: optimize the activation of fast-path tracepoints
Date: Thu, 19 Sep 2024 02:19:08 +0800	[thread overview]
Message-ID: <202409181819.48IIJ84n3584846@localhost.localdomain> (raw)
In-Reply-To: <20240918184502.125550-1-adel.belkhiri@gmail.com>

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

_Compilation OK_

Submitter: Adel Belkhiri <adel.belkhiri@gmail.com>
Date: Wed, 18 Sep 2024 14:45:02 -0400
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 523fd7b3adfdf5a87651e8ca33bc69223b3211d5

144269 --> 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-18 18:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240918184502.125550-1-adel.belkhiri@gmail.com>
2024-09-18 18:19 ` qemudev [this message]
2024-09-18 18:23 ` qemudev
2024-09-18 18:47 ` checkpatch
2024-09-18 19:44 ` 0-day Robot
2024-09-18 21:40 ` |SUCCESS| pw144269 [PATCH] [v3] ethdev: optimize the activation of f dpdklab
2024-09-18 22:16 ` dpdklab
2024-09-18 23:25 ` |FAILURE| " dpdklab
2024-09-19  0:50 ` |PENDING| " dpdklab
2024-09-19  1:01 ` |SUCCESS| " dpdklab
2024-09-19  1:17 ` |PENDING| " dpdklab
2024-09-19  2:07 ` dpdklab
2024-09-19  2:20 ` |SUCCESS| " dpdklab
2024-09-19  3:14 ` dpdklab
2024-09-19  3:57 ` dpdklab
2024-09-19  5:13 ` dpdklab
2024-09-19  5:17 ` dpdklab
2024-09-19  5:25 ` |PENDING| " dpdklab
2024-09-19  5:37 ` |SUCCESS| " dpdklab
2024-09-19  6:20 ` dpdklab
2024-09-19  8:24 ` dpdklab
2024-09-19  8:26 ` dpdklab
2024-09-19  9:00 ` 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=202409181819.48IIJ84n3584846@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).