automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123506-123501 [PATCH v14 6/6] test/memarea: support dump API test
Date: Thu, 9 Feb 2023 14:32:31 +0800	[thread overview]
Message-ID: <202302090632.3196WVqL3969422@localhost.localdomain> (raw)
In-Reply-To: <20230209063610.35501-7-fengchengwen@huawei.com>

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

_Compilation OK_

Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Thu, 9 Feb 2023 06:36:05 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00

123506-123501 --> 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  6:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230209063610.35501-7-fengchengwen@huawei.com>
2023-02-09  6:32 ` qemudev [this message]
2023-02-09  6:36 ` qemudev
2023-02-09  6:44 ` |SUCCESS| pw123501 " checkpatch
2023-02-09  7:59 ` |FAILURE| " 0-day Robot
2023-02-09  7:08 |SUCCESS| pw123506-123501 [PATCH] [v14, " dpdklab
2023-02-09  7:10 dpdklab
2023-02-09  7:12 dpdklab
2023-02-09  7:12 dpdklab
2023-02-09  7:13 dpdklab
2023-02-09  7:17 dpdklab
2023-02-09  7:19 dpdklab
2023-02-09  7:23 dpdklab
2023-02-09  7:25 dpdklab
2023-02-09  7:25 dpdklab
2023-02-09  7:25 dpdklab
2023-02-09  7:29 dpdklab
2023-02-09  7:32 dpdklab
2023-02-09  8:31 dpdklab
2023-02-10 11:14 dpdklab
2023-02-11 21:52 dpdklab
2023-02-12 10:10 dpdklab
2023-02-12 15:16 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=202302090632.3196WVqL3969422@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).