automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture packet coredump
Date: Wed, 20 Mar 2024 00:00:39 +0800	[thread overview]
Message-ID: <202403191600.42JG0dox3394799@localhost.localdomain> (raw)
In-Reply-To: <1710865092-2796-1-git-send-email-junwang01@cestc.cn>

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

_Compilation OK_

Submitter: Jun Wang <junwang01@cestc.cn>
Date: Wed, 20 Mar 2024 00:18:12 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 2c54ea7a59dfc0a819d3527309c62846fc8853af

138484 --> 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-03-19 16:25 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1710865092-2796-1-git-send-email-junwang01@cestc.cn>
2024-03-19 16:00 ` qemudev [this message]
2024-03-19 16:05 ` qemudev
2024-03-19 16:18 ` |WARNING| " checkpatch
2024-03-19 16:55 ` |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture pac dpdklab
2024-03-19 16:55 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:56 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:57 ` dpdklab
2024-03-19 16:58 ` dpdklab
2024-03-19 16:58 ` dpdklab
2024-03-19 16:58 ` dpdklab
2024-03-19 16:59 ` dpdklab
2024-03-19 16:59 ` dpdklab
2024-03-19 16:59 ` dpdklab
2024-03-19 17:00 ` dpdklab
2024-03-19 17:00 ` dpdklab
2024-03-19 17:00 ` dpdklab
2024-03-19 17:01 ` dpdklab
2024-03-19 17:02 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:03 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:04 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:05 ` dpdklab
2024-03-19 17:06 ` dpdklab
2024-03-19 17:06 ` dpdklab
2024-03-19 17:07 ` dpdklab
2024-03-19 17:13 ` dpdklab
2024-03-19 17:13 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:14 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:15 ` dpdklab
2024-03-19 17:16 ` dpdklab
2024-03-19 17:23 ` |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture packet coredump 0-day Robot
2024-03-19 17:25 ` |SUCCESS| pw138484 [PATCH] net/ixgbe: using dpdk-dumpcap capture pac dpdklab
2024-03-19 17:26 ` dpdklab
2024-03-19 17:27 ` dpdklab
2024-03-19 17:27 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:28 ` dpdklab
2024-03-19 17:30 ` dpdklab
2024-03-19 17:30 ` dpdklab
2024-03-19 17:30 ` |FAILURE| " dpdklab
2024-03-19 17:31 ` dpdklab
2024-03-19 17:31 ` |SUCCESS| " dpdklab
2024-03-19 17:32 ` |FAILURE| " dpdklab
2024-03-19 17:36 ` dpdklab
2024-03-19 17:41 ` |SUCCESS| " dpdklab
2024-03-19 17:41 ` dpdklab
2024-03-19 17:52 ` dpdklab
2024-03-19 18:05 ` dpdklab
2024-03-19 18:06 ` |FAILURE| " dpdklab
2024-03-19 18:08 ` |SUCCESS| " dpdklab
2024-03-19 18:11 ` dpdklab
2024-03-19 18:48 ` dpdklab
2024-03-21  5:40 ` dpdklab
2024-03-21  6:05 ` 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=202403191600.42JG0dox3394799@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).