automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw150603-150604 [PATCH v3 2/2] common/idpf: enable AVX2 for single queue Tx
Date: Thu, 30 Jan 2025 15:43:31 +0800	[thread overview]
Message-ID: <202501300743.50U7hV7m2668686@localhost.localdomain> (raw)
In-Reply-To: <20250130082445.1112043-3-shaiq.wani@intel.com>

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

_Compilation OK_

Submitter: Shaiq Wani <shaiq.wani@intel.com>
Date: Thu, 30 Jan 2025 13:54:44 +0530
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 9eb60580d155f5e3a36927dbb1e59ef9623231ce

150603-150604 --> 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-01-30  8:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250130082445.1112043-3-shaiq.wani@intel.com>
2025-01-30  7:43 ` qemudev [this message]
2025-01-30  7:47 ` qemudev
2025-01-30  8:11 ` |SUCCESS| pw150604 " checkpatch
2025-01-30  9:04 ` 0-day Robot
2025-01-30  9:07 ` |PENDING| pw150603-150604 [PATCH] [v3,2/2] common/idpf: enable AVX2 dpdklab
2025-01-30  9:11 ` |SUCCESS| " dpdklab
2025-01-30  9:24 ` dpdklab
2025-01-30  9:24 ` |PENDING| " dpdklab
2025-01-30  9:24 ` |SUCCESS| " dpdklab
2025-01-30  9:26 ` |PENDING| " dpdklab
2025-01-30  9:37 ` |SUCCESS| " dpdklab
2025-01-30 10:10 ` dpdklab
2025-01-30 10:16 ` dpdklab
2025-01-30 10:43 ` |WARNING| " dpdklab
2025-01-30 11:15 ` |SUCCESS| " dpdklab
2025-01-30 11:16 ` dpdklab
2025-01-30 13:14 ` dpdklab
2025-02-04 18:08 ` dpdklab
2025-02-05  4:37 ` |WARNING| " dpdklab
2025-02-05 16:52 ` |SUCCESS| " dpdklab
2025-02-06 12:30 ` 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=202501300743.50U7hV7m2668686@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).