automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123575-123577 [PATCH v7 3/3] examples/l3fwd-graph: changes to configure pcap capture
Date: Thu, 9 Feb 2023 18:17:08 +0800	[thread overview]
Message-ID: <202302091017.319AH8Eb161046@localhost.localdomain> (raw)
In-Reply-To: <20230209102434.2460394-3-amitprakashs@marvell.com>

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

_Compilation OK_

Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Thu, 9 Feb 2023 15:54:32 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 21fc3d765c12a517cea70dcf98bc08123e07df33

123575-123577 --> 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:[~2023-02-09 10:30 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230209102434.2460394-3-amitprakashs@marvell.com>
2023-02-09 10:17 ` qemudev [this message]
2023-02-09 10:21 ` qemudev
2023-02-09 10:26 ` |SUCCESS| pw123577 " checkpatch
2023-02-09 11:39 ` 0-day Robot
2023-02-17 15:23 |SUCCESS| pw123575-123577 [PATCH] [v7, " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-02-12 20:44 dpdklab
2023-02-12 10:43 dpdklab
2023-02-10 20:02 dpdklab
2023-02-10 20:01 dpdklab
2023-02-10 20:00 dpdklab
2023-02-10 19:58 dpdklab
2023-02-10 19:56 dpdklab
2023-02-10 19:55 dpdklab
2023-02-10 19:54 dpdklab
2023-02-10 19:51 dpdklab
2023-02-10 19:51 dpdklab
2023-02-10 19:45 dpdklab
2023-02-10 19:45 dpdklab
2023-02-10 19:35 dpdklab
2023-02-10 19:27 dpdklab
2023-02-10 19:03 dpdklab
2023-02-09 15:10 dpdklab
2023-02-09 11:58 dpdklab
2023-02-09 11:50 dpdklab
2023-02-09 11:42 dpdklab
2023-02-09 11:26 dpdklab
2023-02-09 11:11 dpdklab
2023-02-09 11:06 dpdklab
2023-02-09 11:05 dpdklab
2023-02-09 11:01 dpdklab
2023-02-09 10:59 dpdklab
2023-02-09 10:58 dpdklab
2023-02-09 10:58 dpdklab
2023-02-09 10:54 dpdklab
2023-02-09 10:50 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=202302091017.319AH8Eb161046@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).