automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125194 [PATCH v2 1/1] ml/cnxk: fix reporting of incorrect error info
Date: Fri, 17 Mar 2023 01:14:44 +0800	[thread overview]
Message-ID: <202303161714.32GHEihi538883@localhost.localdomain> (raw)
In-Reply-To: <20230316172215.20067-1-syalavarthi@marvell.com>

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

_Compilation OK_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Thu, 16 Mar 2023 10:22:15 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: bb1f2f5b181b9d8ea7fb28ca2024914fc57bd823

125194 --> 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-03-16 17:28 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230316172215.20067-1-syalavarthi@marvell.com>
2023-03-16 17:14 ` qemudev [this message]
2023-03-16 17:18 ` qemudev
2023-03-16 17:23 ` checkpatch
2023-03-16 20:00 ` 0-day Robot
2023-03-16 19:02 |SUCCESS| pw125194 [PATCH] [v2, " dpdklab
2023-03-16 19:09 dpdklab
2023-03-16 19:15 dpdklab
2023-03-16 19:16 dpdklab
2023-03-16 19:21 dpdklab
2023-03-16 19:23 dpdklab
2023-03-16 19:31 dpdklab
2023-03-16 19:37 dpdklab
2023-03-16 19:39 dpdklab
2023-03-16 19:47 dpdklab
2023-03-16 19:51 dpdklab
2023-03-16 19:59 dpdklab
2023-03-16 20:02 dpdklab
2023-03-16 20:07 dpdklab
2023-03-16 20:12 dpdklab
2023-03-16 20:22 dpdklab
2023-03-16 20:26 dpdklab
2023-03-16 20:32 dpdklab
2023-03-16 20:33 dpdklab
2023-03-16 20:45 dpdklab
2023-03-16 20:58 dpdklab
2023-03-16 21:15 dpdklab
2023-03-16 21:49 dpdklab
2023-03-16 22:01 dpdklab
2023-03-16 22:22 dpdklab
2023-03-16 22:35 dpdklab
2023-03-17  0:17 dpdklab
2023-03-17  0:25 dpdklab
2023-03-17  0:43 dpdklab
2023-03-17  1:14 dpdklab
2023-03-17 16:41 dpdklab
2023-03-17 16:47 dpdklab
2023-03-18 22:26 dpdklab
2023-03-18 22:26 dpdklab
2023-03-18 23:59 dpdklab
2023-03-19  0:44 dpdklab
2023-03-19  8:28 dpdklab
2023-03-19  9:02 dpdklab
2023-03-19  9:04 dpdklab
2023-03-19  9:13 dpdklab
2023-03-19  9:16 dpdklab
2023-03-19  9:19 dpdklab
2023-03-19  9:20 dpdklab
2023-03-19  9:32 dpdklab
2023-03-19  9:32 dpdklab
2023-03-19  9:34 dpdklab
2023-03-19  9:36 dpdklab
2023-03-19  9:45 dpdklab
2023-03-19  9:47 dpdklab
2023-03-19  9:48 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=202303161714.32GHEihi538883@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).