automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138105-138103 [PATCH v2 5/5] test/argparse: refine testcases
Date: Thu, 7 Mar 2024 20:47:31 +0800	[thread overview]
Message-ID: <202403071247.427ClVhw336781@localhost.localdomain> (raw)
In-Reply-To: <20240307130742.5578-6-fengchengwen@huawei.com>

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

_Compilation OK_

Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Thu, 7 Mar 2024 13:07:38 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 19082c1fac430c74bb4b1c101edd12d88928e7c2

138105-138103 --> 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-07 13:12 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240307130742.5578-6-fengchengwen@huawei.com>
2024-03-07 12:47 ` qemudev [this message]
2024-03-07 12:51 ` qemudev
2024-03-07 13:11 ` |SUCCESS| pw138103 " checkpatch
2024-03-07 14:04 ` 0-day Robot
2024-03-07 15:01 ` |SUCCESS| pw138105-138103 [PATCH] [v2,5/5] test/argparse: refine tes dpdklab
2024-03-07 15:26 ` dpdklab
2024-03-07 15:30 ` dpdklab
2024-03-07 15:38 ` dpdklab
2024-03-07 15:55 ` dpdklab
2024-03-07 16:01 ` dpdklab
2024-03-07 16:03 ` dpdklab
2024-03-07 16:03 ` dpdklab
2024-03-07 16:13 ` dpdklab
2024-03-07 16:13 ` dpdklab
2024-03-07 16:14 ` dpdklab
2024-03-07 16:15 ` dpdklab
2024-03-07 16:18 ` dpdklab
2024-03-07 16:18 ` dpdklab
2024-03-07 16:19 ` dpdklab
2024-03-07 16:21 ` dpdklab
2024-03-07 16:21 ` dpdklab
2024-03-07 16:23 ` dpdklab
2024-03-07 16:42 ` dpdklab
2024-03-07 16:46 ` dpdklab
2024-03-07 16:53 ` dpdklab
2024-03-07 16:54 ` dpdklab
2024-03-07 16:57 ` dpdklab
2024-03-07 17:00 ` dpdklab
2024-03-07 17:20 ` dpdklab
2024-03-07 17:31 ` dpdklab
2024-03-07 17:34 ` dpdklab
2024-03-07 17:37 ` dpdklab
2024-03-07 17:41 ` dpdklab
2024-03-07 17:48 ` dpdklab
2024-03-07 18:02 ` dpdklab
2024-03-07 18:04 ` dpdklab
2024-03-07 18:06 ` dpdklab
2024-03-07 18:07 ` dpdklab
2024-03-07 18:07 ` dpdklab
2024-03-07 18:10 ` dpdklab
2024-03-07 18:11 ` dpdklab
2024-03-07 18:11 ` dpdklab
2024-03-07 18:13 ` dpdklab
2024-03-07 18:13 ` dpdklab
2024-03-07 18:14 ` dpdklab
2024-03-07 18:15 ` dpdklab
2024-03-07 18:17 ` dpdklab
2024-03-07 18:17 ` dpdklab
2024-03-07 18:17 ` dpdklab
2024-03-07 18:17 ` dpdklab
2024-03-07 18:18 ` dpdklab
2024-03-07 18:18 ` dpdklab
2024-03-07 18:19 ` dpdklab
2024-03-07 18:19 ` dpdklab
2024-03-07 18:20 ` dpdklab
2024-03-07 18:20 ` dpdklab
2024-03-07 18:20 ` dpdklab
2024-03-07 18:22 ` dpdklab
2024-03-07 18:22 ` dpdklab
2024-03-07 18:22 ` dpdklab
2024-03-07 18:24 ` dpdklab
2024-03-07 18:26 ` dpdklab
2024-03-07 18:27 ` dpdklab
2024-03-07 18:27 ` dpdklab
2024-03-07 18:30 ` dpdklab
2024-03-07 18:31 ` dpdklab
2024-03-07 18:32 ` dpdklab
2024-03-07 18:32 ` dpdklab
2024-03-07 18:41 ` dpdklab
2024-03-07 18:42 ` dpdklab
2024-03-07 18:42 ` dpdklab
2024-03-07 18:52 ` dpdklab
2024-03-07 18:52 ` dpdklab
2024-03-07 18:53 ` dpdklab
2024-03-07 18:54 ` dpdklab
2024-03-07 18:54 ` dpdklab
2024-03-07 18:54 ` dpdklab
2024-03-07 18:54 ` dpdklab
2024-03-07 18:58 ` dpdklab
2024-03-07 19:11 ` dpdklab
2024-03-07 20:22 ` dpdklab
2024-03-07 21:30 ` dpdklab
2024-03-08  0:17 ` dpdklab
2024-03-08  7:48 ` dpdklab
2024-03-08  7:51 ` dpdklab
2024-03-08  7:52 ` dpdklab
2024-03-08  7:55 ` dpdklab
2024-03-12  3:34 ` dpdklab
2024-03-12  4:26 ` 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=202403071247.427ClVhw336781@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).