automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144301 [PATCH v3] dts: fix runner target in the Dockerfile
Date: Thu, 19 Sep 2024 21:59:07 +0800	[thread overview]
Message-ID: <202409191359.48JDx7tb002915@localhost.localdomain> (raw)
In-Reply-To: <20240919142438.10192-1-jspewock@iol.unh.edu>

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

_Compilation OK_

Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Thu, 19 Sep 2024 10:24:38 -0400
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

144301 --> 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-09-19 14:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240919142438.10192-1-jspewock@iol.unh.edu>
2024-09-19 13:59 ` qemudev [this message]
2024-09-19 14:03 ` qemudev
2024-09-19 14:25 ` checkpatch
2024-09-19 19:42 ` |SUCCESS| pw144301 [PATCH] [v3] dts: fix runner target in the Docker dpdklab
2024-09-19 19:44 ` dpdklab
2024-09-19 19:58 ` dpdklab
2024-09-19 20:24 ` dpdklab
2024-09-19 20:51 ` dpdklab
2024-09-19 20:55 ` |PENDING| " dpdklab
2024-09-19 21:06 ` dpdklab
2024-09-19 21:11 ` |SUCCESS| " dpdklab
2024-09-19 21:20 ` dpdklab
2024-09-19 21:44 ` dpdklab
2024-09-20  0:20 ` dpdklab
2024-09-20  1:42 ` dpdklab
2024-09-20  3:19 ` dpdklab
2024-09-20  3:44 ` dpdklab
2024-09-21  6:53 ` dpdklab
2024-09-23  5:03 ` dpdklab
2024-09-23  5: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=202409191359.48JDx7tb002915@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).