automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw149561-149562 [PATCH v9 3/3] drivers/net: add diagnostics macros to make code portable
Date: Wed, 1 Jan 2025 11:05:19 +0800	[thread overview]
Message-ID: <202501010305.50135Jm7011149@localhost.localdomain> (raw)
In-Reply-To: <1735702586-24837-4-git-send-email-andremue@linux.microsoft.com>

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

_Compilation OK_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Tue, 31 Dec 2024 19:36:24 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: fd51012de5369679e807be1d6a81d63ef15015ce

149561-149562 --> 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-01  3:38 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1735702586-24837-4-git-send-email-andremue@linux.microsoft.com>
2025-01-01  3:05 ` qemudev [this message]
2025-01-01  3:10 ` qemudev
2025-01-01  3:37 ` |WARNING| pw149562 " checkpatch
2025-01-01  4:24 ` |SUCCESS| " 0-day Robot
2025-01-02 21:04 ` |PENDING| pw149561-149562 [PATCH] [v9,3/3] drivers/net: add diagnost dpdklab
2025-01-02 21:06 ` |FAILURE| " dpdklab
2025-01-02 21:30 ` |SUCCESS| " dpdklab
2025-01-02 21:32 ` |FAILURE| " dpdklab
2025-01-02 21:36 ` dpdklab
2025-01-02 21:44 ` dpdklab
2025-01-02 21:44 ` dpdklab
2025-01-02 21:50 ` dpdklab
2025-01-02 21:51 ` |SUCCESS| " dpdklab
2025-01-02 21:53 ` dpdklab
2025-01-02 21:53 ` dpdklab
2025-01-02 21:55 ` |FAILURE| " dpdklab
2025-01-02 22:01 ` |WARNING| " dpdklab
2025-01-02 22:06 ` |SUCCESS| " dpdklab
2025-01-02 22:26 ` |PENDING| " dpdklab
2025-01-02 22:30 ` |SUCCESS| " dpdklab
2025-01-02 22:30 ` |FAILURE| " dpdklab
2025-01-02 22:31 ` |SUCCESS| " dpdklab
2025-01-02 22:37 ` |FAILURE| " dpdklab
2025-01-02 22:42 ` dpdklab
2025-01-02 22:43 ` dpdklab
2025-01-02 22:52 ` |SUCCESS| " dpdklab
2025-01-02 22:57 ` |FAILURE| " dpdklab
2025-01-02 22:58 ` |WARNING| " dpdklab
2025-01-02 23:00 ` |SUCCESS| " dpdklab
2025-01-02 23:11 ` |FAILURE| " dpdklab
2025-01-02 23:12 ` dpdklab
2025-01-02 23:30 ` dpdklab
2025-01-02 23:42 ` |SUCCESS| " dpdklab
2025-01-03  2:08 ` dpdklab
2025-01-06 19:21 ` |PENDING| " dpdklab
2025-01-06 19:46 ` |SUCCESS| " 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=202501010305.50135Jm7011149@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).