automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137661 [PATCH v3] net/ice: add diagnostic support in TX path
Date: Sat, 2 Mar 2024 14:27:29 +0800	[thread overview]
Message-ID: <202403020627.4226RTmC3907532@localhost.localdomain> (raw)
In-Reply-To: <20240301095052.460597-1-mingjinx.ye@intel.com>

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

_Compilation OK_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Fri,  1 Mar 2024 09:50:51 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 3408b132b31906fe1ed28d6b2009b98202e1cff0

137661 --> 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


  parent reply	other threads:[~2024-03-02  6:52 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301095052.460597-1-mingjinx.ye@intel.com>
2024-03-01 10:12 ` checkpatch
2024-03-01 11:05 ` 0-day Robot
2024-03-01 14:26 ` |SUCCESS| pw137661 [PATCH] [v3] net/ice: add diagnostic support in T dpdklab
2024-03-01 14:35 ` |FAILURE| " dpdklab
2024-03-01 15:05 ` |SUCCESS| " dpdklab
2024-03-01 15:15 ` |FAILURE| " dpdklab
2024-03-01 15:18 ` |SUCCESS| " dpdklab
2024-03-01 15:21 ` dpdklab
2024-03-01 15:21 ` dpdklab
2024-03-01 15:21 ` dpdklab
2024-03-01 15:23 ` |FAILURE| " dpdklab
2024-03-01 15:27 ` |SUCCESS| " dpdklab
2024-03-01 15:28 ` dpdklab
2024-03-01 15:42 ` dpdklab
2024-03-01 15:45 ` dpdklab
2024-03-01 15:45 ` dpdklab
2024-03-01 15:47 ` dpdklab
2024-03-01 15:47 ` dpdklab
2024-03-01 15:49 ` dpdklab
2024-03-01 15:58 ` dpdklab
2024-03-01 16:30 ` dpdklab
2024-03-01 16:37 ` dpdklab
2024-03-01 16:39 ` dpdklab
2024-03-01 16:41 ` dpdklab
2024-03-01 16:41 ` dpdklab
2024-03-01 16:42 ` dpdklab
2024-03-01 16:43 ` dpdklab
2024-03-01 16:49 ` dpdklab
2024-03-01 16:49 ` dpdklab
2024-03-01 16:49 ` dpdklab
2024-03-01 16:49 ` dpdklab
2024-03-01 16:49 ` dpdklab
2024-03-01 16:50 ` dpdklab
2024-03-01 16:50 ` dpdklab
2024-03-01 16:50 ` dpdklab
2024-03-01 16:52 ` dpdklab
2024-03-01 16:53 ` dpdklab
2024-03-01 16:53 ` dpdklab
2024-03-01 16:53 ` dpdklab
2024-03-01 16:53 ` dpdklab
2024-03-01 16:53 ` dpdklab
2024-03-01 16:54 ` dpdklab
2024-03-01 16:55 ` dpdklab
2024-03-01 16:55 ` dpdklab
2024-03-01 16:55 ` dpdklab
2024-03-01 16:56 ` dpdklab
2024-03-01 17:05 ` dpdklab
2024-03-01 17:05 ` dpdklab
2024-03-01 17:06 ` dpdklab
2024-03-01 17:07 ` dpdklab
2024-03-01 17:08 ` dpdklab
2024-03-01 17:09 ` dpdklab
2024-03-01 17:10 ` dpdklab
2024-03-01 17:10 ` dpdklab
2024-03-01 17:10 ` dpdklab
2024-03-01 17:11 ` dpdklab
2024-03-01 17:12 ` dpdklab
2024-03-01 17:12 ` dpdklab
2024-03-01 17:14 ` dpdklab
2024-03-01 17:14 ` dpdklab
2024-03-01 17:14 ` dpdklab
2024-03-01 17:14 ` dpdklab
2024-03-01 17:15 ` dpdklab
2024-03-01 17:15 ` dpdklab
2024-03-01 17:33 ` dpdklab
2024-03-01 18:07 ` dpdklab
2024-03-01 18:41 ` |FAILURE| " dpdklab
2024-03-01 18:45 ` |SUCCESS| " dpdklab
2024-03-01 18:54 ` dpdklab
2024-03-01 18:55 ` dpdklab
2024-03-01 18:57 ` |FAILURE| " dpdklab
2024-03-01 19:12 ` |SUCCESS| " dpdklab
2024-03-01 19:21 ` dpdklab
2024-03-02  2:44 ` dpdklab
2024-03-02  2:50 ` dpdklab
2024-03-02  6:27 ` qemudev [this message]
2024-03-02  6:32 ` |SUCCESS| pw137661 [PATCH v3] net/ice: add diagnostic support in TX path qemudev
2024-03-02 18:48 ` |SUCCESS| pw137661 [PATCH] [v3] net/ice: add diagnostic support in T dpdklab
2024-03-05  6:02 ` dpdklab
2024-03-05  6:34 ` dpdklab
2024-03-05  7:07 ` 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=202403020627.4226RTmC3907532@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).