automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120413-120414 [PATCH v3 2/2] build: generate Windows build artefacts when needed
Date: Thu, 1 Dec 2022 18:01:57 +0800	[thread overview]
Message-ID: <202212011001.2B1A1v8a3975601@localhost.localdomain> (raw)
In-Reply-To: <20221201100847.322141-2-david.marchand@redhat.com>

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

_Compilation OK_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Thu,  1 Dec 2022 11:08:46 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: f262f16087ea6a77357a915cf4c0d10ddc7b6562

120413-120414 --> 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:[~2022-12-01 10:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221201100847.322141-2-david.marchand@redhat.com>
2022-12-01 10:01 ` qemudev [this message]
2022-12-01 10:05 ` qemudev
2022-12-01 10:10 ` |SUCCESS| pw120414 " checkpatch
2022-12-01 10:58 ` 0-day Robot
2022-12-01 10:39 |SUCCESS| pw120413-120414 [PATCH] [v3, " dpdklab
2022-12-01 10:40 dpdklab
2022-12-01 10:46 dpdklab
2022-12-01 10:52 dpdklab
2022-12-01 10:55 dpdklab
2022-12-01 11:00 dpdklab
2022-12-01 11:00 dpdklab
2022-12-01 11:41 dpdklab
2022-12-03  2:01 dpdklab
2022-12-03  2:05 dpdklab
2022-12-03  2:05 dpdklab
2022-12-03  2:25 dpdklab
2022-12-03  2:25 dpdklab
2022-12-03  2:25 dpdklab
2022-12-03  2:26 dpdklab
2022-12-03 14:25 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=202212011001.2B1A1v8a3975601@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).