automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120436-120437 [PATCH v4 2/2] build: generate Windows build artefacts when needed
Date: Fri, 2 Dec 2022 21:19:55 +0800	[thread overview]
Message-ID: <202212021319.2B2DJteu232114@localhost.localdomain> (raw)
In-Reply-To: <20221202110945.519708-2-david.marchand@redhat.com>

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

_Compilation OK_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Fri,  2 Dec 2022 12:09:43 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 7b1934d01a1a8afa1391f361088d8285d100e62a

120436-120437 --> 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


  parent reply	other threads:[~2022-12-02 13:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221202110945.519708-2-david.marchand@redhat.com>
2022-12-02 11:11 ` |SUCCESS| pw120437 " checkpatch
2022-12-02 12:38 ` 0-day Robot
2022-12-02 13:19 ` qemudev [this message]
2022-12-02 13:23 ` |SUCCESS| pw120436-120437 " qemudev
2022-12-02 20:00 |SUCCESS| pw120436-120437 [PATCH] [v4, " dpdklab
2022-12-02 20:05 dpdklab
2022-12-02 20:12 dpdklab
2022-12-02 20:21 dpdklab
2022-12-02 20:26 dpdklab
2022-12-02 22:12 dpdklab
2022-12-03 11:02 dpdklab
2022-12-03 11:03 dpdklab
2022-12-03 11:07 dpdklab
2022-12-03 11:08 dpdklab
2022-12-03 11:08 dpdklab
2022-12-03 11:47 dpdklab
2022-12-03 11:47 dpdklab
2022-12-03 11:47 dpdklab
2022-12-03 11:48 dpdklab
2022-12-03 22:14 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=202212021319.2B2DJteu232114@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).