automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147438 [PATCH] dumpcap: check return value from adding interface
Date: Mon, 28 Oct 2024 01:57:07 +0800	[thread overview]
Message-ID: <202410271757.49RHv7An2447352@localhost.localdomain> (raw)
In-Reply-To: <20241027182903.209391-1-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sun, 27 Oct 2024 11:28:48 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 6dad0bb5c8621644beca86ff5f4910a943ba604d

147438 --> 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-10-27 18:30 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241027182903.209391-1-stephen@networkplumber.org>
2024-10-27 17:57 ` qemudev [this message]
2024-10-27 18:01 ` qemudev
2024-10-27 18:30 ` |WARNING| " checkpatch
2024-10-27 19:26 ` |SUCCESS| " 0-day Robot
2024-10-28  0:23 ` |SUCCESS| pw147438 [PATCH] dumpcap: check return value from adding i dpdklab
2024-10-28  0:30 ` dpdklab
2024-10-28  0:34 ` dpdklab
2024-10-28  0:37 ` dpdklab
2024-10-28  0:37 ` dpdklab
2024-10-28  0:38 ` dpdklab
2024-10-28  1:47 ` |PENDING| " dpdklab
2024-10-28  1:49 ` |SUCCESS| " dpdklab
2024-10-28  2:13 ` dpdklab
2024-10-28  6:06 ` |WARNING| " dpdklab
2024-10-28  7:17 ` dpdklab
2024-10-28  7:38 ` |SUCCESS| " dpdklab
2024-10-28  7:43 ` dpdklab
2024-10-28  7:45 ` |WARNING| " dpdklab
2024-10-28  7:47 ` |SUCCESS| " dpdklab
2024-10-28  8:06 ` dpdklab
2024-10-28  8:44 ` dpdklab
2024-10-28  9:00 ` |WARNING| " dpdklab
2024-10-28  9:34 ` dpdklab
2024-10-28  9:50 ` dpdklab
2024-10-28  9:57 ` dpdklab
2024-10-28 11:11 ` dpdklab
2024-10-28 11:28 ` dpdklab
2024-10-28 11:41 ` dpdklab
2024-10-28 12:02 ` dpdklab
2024-10-28 13:40 ` dpdklab
2024-10-28 15:04 ` dpdklab
2024-10-28 15:24 ` |SUCCESS| " dpdklab
2024-10-28 15:34 ` dpdklab
2024-10-28 17:45 ` dpdklab
2024-10-29 21:39 ` |PENDING| " dpdklab
2024-10-29 22:54 ` |SUCCESS| " dpdklab
2024-10-30  4:00 ` dpdklab
2024-10-30  6:45 ` dpdklab
2024-10-30  6:45 ` dpdklab
2024-10-30 12:23 ` dpdklab
2024-10-30 21:40 ` 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=202410271757.49RHv7An2447352@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).