automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139757 [PATCH] maintainers: update for eal
Date: Wed, 1 May 2024 04:25:56 +0800	[thread overview]
Message-ID: <202404302025.43UKPuGR3615525@localhost.localdomain> (raw)
In-Reply-To: <1714510339-10416-1-git-send-email-roretzla@linux.microsoft.com>

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

_Compilation OK_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tue, 30 Apr 2024 13:52:19 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139757 --> 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-30 20:53 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1714510339-10416-1-git-send-email-roretzla@linux.microsoft.com>
2024-04-30 20:25 ` qemudev [this message]
2024-04-30 20:30 ` qemudev
2024-04-30 21:39 ` dpdklab
2024-04-30 21:39 ` dpdklab
2024-04-30 21:40 ` dpdklab
2024-04-30 21:40 ` dpdklab
2024-04-30 21:41 ` dpdklab
2024-04-30 21:41 ` dpdklab
2024-04-30 21:42 ` dpdklab
2024-04-30 21:43 ` 0-day Robot
2024-04-30 21:46 ` dpdklab
2024-04-30 21:47 ` dpdklab
2024-04-30 21:47 ` dpdklab
2024-04-30 21:47 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:48 ` dpdklab
2024-04-30 21:49 ` dpdklab
2024-04-30 21:49 ` dpdklab
2024-04-30 21:49 ` dpdklab
2024-04-30 21:49 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:50 ` dpdklab
2024-04-30 21:51 ` dpdklab
2024-04-30 21:51 ` dpdklab
2024-04-30 21:51 ` dpdklab
2024-04-30 21:51 ` dpdklab
2024-04-30 21:52 ` dpdklab
2024-04-30 21:54 ` dpdklab
2024-04-30 21:54 ` dpdklab
2024-04-30 21:54 ` dpdklab
2024-04-30 21:55 ` dpdklab
2024-04-30 21:55 ` dpdklab
2024-04-30 21:55 ` dpdklab
2024-04-30 21:56 ` dpdklab
2024-04-30 21:56 ` dpdklab
2024-04-30 21:56 ` dpdklab
2024-04-30 21:56 ` dpdklab
2024-04-30 21:57 ` dpdklab
2024-04-30 21:57 ` dpdklab
2024-04-30 21:57 ` dpdklab
2024-04-30 21:58 ` dpdklab
2024-04-30 21:58 ` dpdklab
2024-04-30 21:58 ` dpdklab
2024-04-30 21:58 ` dpdklab
2024-04-30 21:59 ` dpdklab
2024-04-30 22:00 ` dpdklab
2024-04-30 22:01 ` dpdklab
2024-04-30 22:01 ` dpdklab
2024-04-30 22:01 ` dpdklab
2024-04-30 22:02 ` dpdklab
2024-04-30 22:02 ` dpdklab
2024-04-30 22:06 ` dpdklab
2024-04-30 22:06 ` dpdklab
2024-04-30 22:06 ` dpdklab
2024-04-30 22:07 ` dpdklab
2024-04-30 22:07 ` dpdklab
2024-04-30 22:20 ` dpdklab
2024-04-30 22:23 ` dpdklab
2024-04-30 22:23 ` dpdklab
2024-04-30 22:24 ` dpdklab
2024-04-30 22:24 ` dpdklab
2024-04-30 22:24 ` dpdklab
2024-04-30 22:25 ` dpdklab
2024-04-30 22:26 ` dpdklab
2024-04-30 22:26 ` dpdklab
2024-04-30 22:28 ` dpdklab
2024-04-30 22:28 ` dpdklab
2024-04-30 22:31 ` dpdklab
2024-04-30 22:32 ` dpdklab
2024-04-30 22:33 ` dpdklab
2024-04-30 22:35 ` dpdklab
2024-04-30 22:36 ` dpdklab
2024-04-30 23:06 ` dpdklab
2024-04-30 23:06 ` dpdklab
2024-04-30 23:12 ` dpdklab
2024-05-01 21:38 ` dpdklab
2024-05-02 20:06 ` dpdklab
2024-05-03 15:16 ` dpdklab
2024-05-03 20:33 ` dpdklab
2024-05-05  8:12 ` dpdklab
2024-05-05  8:17 ` dpdklab
2024-05-05  8:21 ` 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=202404302025.43UKPuGR3615525@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).