automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143465-143498 [PATCH 47/47] net/bnxt: tf_ulp: add stats cache for thor2
Date: Fri, 30 Aug 2024 22:55:14 +0800	[thread overview]
Message-ID: <202408301455.47UEtE5j3883436@localhost.localdomain> (raw)
In-Reply-To: <20240830140049.1715230-48-sriharsha.basavapatna@broadcom.com>

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

_Compilation OK_

Submitter: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Date: Fri, 30 Aug 2024 19:30:03 +0530
DPDK git baseline: Repo:dpdk-next-net-brcm
  Branch: for-next-net
  CommitID: 077056ef50ec8e3717e4afcb6f89dcb77110e663

143465-143498 --> 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-08-30 15:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240830140049.1715230-48-sriharsha.basavapatna@broadcom.com>
2024-08-30 14:11 ` |WARNING| pw143498 " checkpatch
2024-08-30 14:39 ` |SUCCESS| pw143465-143498 [PATCH] [47/47] net/bnxt: tf_ulp: add stat dpdklab
2024-08-30 14:40 ` |PENDING| " dpdklab
2024-08-30 14:45 ` dpdklab
2024-08-30 14:48 ` dpdklab
2024-08-30 14:49 ` |SUCCESS| " dpdklab
2024-08-30 14:55 ` qemudev [this message]
2024-08-30 14:59 ` |PENDING| " dpdklab
2024-08-30 14:59 ` |SUCCESS| pw143465-143498 [PATCH 47/47] net/bnxt: tf_ulp: add stats cache for thor2 qemudev
2024-08-30 15:04 ` |FAILURE| pw143498 " 0-day Robot
2024-08-30 15:11 ` |SUCCESS| pw143465-143498 [PATCH] [47/47] net/bnxt: tf_ulp: add stat dpdklab
2024-08-30 15:14 ` |FAILURE| " dpdklab
2024-08-30 15:15 ` dpdklab
2024-08-30 15:15 ` dpdklab
2024-08-30 15:15 ` |SUCCESS| " dpdklab
2024-08-30 15:15 ` |FAILURE| " dpdklab
2024-08-30 15:16 ` |SUCCESS| " dpdklab
2024-08-30 15:16 ` dpdklab
2024-08-30 15:16 ` dpdklab
2024-08-30 15:17 ` dpdklab
2024-08-30 15:20 ` |FAILURE| " dpdklab
2024-08-30 15:26 ` |WARNING| " dpdklab
2024-08-30 15:27 ` dpdklab
2024-08-30 15:29 ` |SUCCESS| " dpdklab
2024-08-30 15:36 ` dpdklab
2024-08-30 15:39 ` |WARNING| " dpdklab
2024-08-30 15:46 ` |FAILURE| " dpdklab
2024-09-19  6:03 ` |SUCCESS| " dpdklab
2024-09-19  6:22 ` 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=202408301455.47UEtE5j3883436@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).