automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139135-139164 [PATCH v4 30/30] examples: replace use of fixed size rte_memcpy
Date: Sat, 6 Apr 2024 00:52:46 +0800	[thread overview]
Message-ID: <202404051652.435GqkCH3147600@localhost.localdomain> (raw)
In-Reply-To: <20240405165518.367503-31-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri,  5 Apr 2024 09:53:12 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139135-139164 --> 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-04-05 17:17 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240405165518.367503-31-stephen@networkplumber.org>
2024-04-05 16:52 ` qemudev [this message]
2024-04-05 16:57 ` qemudev
2024-04-05 17:02 ` |WARNING| pw139164 " checkpatch
2024-04-05 17:37 ` |SUCCESS| pw139135-139164 [PATCH] [v4,30/30] examples: replace use o dpdklab
2024-04-05 17:37 ` dpdklab
2024-04-05 17:38 ` dpdklab
2024-04-05 17:38 ` dpdklab
2024-04-05 17:39 ` dpdklab
2024-04-05 17:39 ` dpdklab
2024-04-05 17:40 ` dpdklab
2024-04-05 17:40 ` dpdklab
2024-04-05 17:40 ` dpdklab
2024-04-05 17:40 ` dpdklab
2024-04-05 17:41 ` dpdklab
2024-04-05 17:41 ` dpdklab
2024-04-05 17:42 ` dpdklab
2024-04-05 17:42 ` dpdklab
2024-04-05 17:43 ` dpdklab
2024-04-05 17:43 ` dpdklab
2024-04-05 17:44 ` dpdklab
2024-04-05 17:45 ` dpdklab
2024-04-05 17:45 ` dpdklab
2024-04-05 17:45 ` dpdklab
2024-04-05 17:45 ` dpdklab
2024-04-05 17:46 ` dpdklab
2024-04-05 17:46 ` dpdklab
2024-04-05 17:46 ` dpdklab
2024-04-05 17:46 ` dpdklab
2024-04-05 17:46 ` dpdklab
2024-04-05 17:46 ` dpdklab
2024-04-05 17:52 ` dpdklab
2024-04-05 17:53 ` dpdklab
2024-04-05 17:55 ` dpdklab
2024-04-05 17:58 ` dpdklab
2024-04-05 17:58 ` dpdklab
2024-04-05 17:58 ` dpdklab
2024-04-05 17:59 ` dpdklab
2024-04-05 17:59 ` dpdklab
2024-04-05 17:59 ` dpdklab
2024-04-05 18:00 ` dpdklab
2024-04-05 18:00 ` dpdklab
2024-04-05 18:00 ` dpdklab
2024-04-05 18:00 ` dpdklab
2024-04-05 18:01 ` dpdklab
2024-04-05 18:01 ` dpdklab
2024-04-05 18:02 ` dpdklab
2024-04-05 18:02 ` dpdklab
2024-04-05 18:03 ` dpdklab
2024-04-05 18:03 ` dpdklab
2024-04-05 18:03 ` dpdklab
2024-04-05 18:04 ` dpdklab
2024-04-05 18:05 ` dpdklab
2024-04-05 18:07 ` dpdklab
2024-04-05 18:07 ` dpdklab
2024-04-05 18:08 ` dpdklab
2024-04-05 18:08 ` dpdklab
2024-04-05 18:08 ` dpdklab
2024-04-05 18:09 ` dpdklab
2024-04-05 18:09 ` dpdklab
2024-04-05 18:09 ` dpdklab
2024-04-05 18:09 ` dpdklab
2024-04-05 18:10 ` dpdklab
2024-04-05 18:10 ` dpdklab
2024-04-05 18:11 ` dpdklab
2024-04-05 18:11 ` dpdklab
2024-04-05 18:16 ` dpdklab
2024-04-05 18:16 ` dpdklab
2024-04-05 18:23 ` dpdklab
2024-04-05 18:32 ` dpdklab
2024-04-05 18:33 ` dpdklab
2024-04-05 18:33 ` dpdklab
2024-04-05 18:33 ` dpdklab
2024-04-05 18:33 ` dpdklab
2024-04-05 18:34 ` dpdklab
2024-04-05 18:38 ` dpdklab
2024-04-05 18:38 ` dpdklab
2024-04-05 18:39 ` dpdklab
2024-04-05 18:40 ` dpdklab
2024-04-05 18:40 ` dpdklab
2024-04-05 18:41 ` dpdklab
2024-04-05 18:42 ` dpdklab
2024-04-05 18:47 ` dpdklab
2024-04-05 18:57 ` dpdklab
2024-04-05 19:11 ` dpdklab
2024-04-05 19:30 ` dpdklab
2024-04-05 19:34 ` dpdklab
2024-04-05 19:38 ` dpdklab
2024-04-05 19:42 ` dpdklab
2024-04-05 20:19 ` dpdklab
2024-04-05 21:04 ` |SUCCESS| pw139164 [PATCH v4 30/30] examples: replace use of fixed size rte_memcpy 0-day Robot
2024-04-05 22:10 ` |SUCCESS| pw139135-139164 [PATCH] [v4,30/30] examples: replace use o dpdklab
2024-04-05 22:29 ` 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=202404051652.435GqkCH3147600@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).