automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123296 [PATCH] build: fix invalid characters in toolchain definitions
Date: Tue, 7 Feb 2023 23:17:01 +0800	[thread overview]
Message-ID: <202302071517.317FH1PA799782@localhost.localdomain> (raw)
In-Reply-To: <20230207152200.122227-1-bruce.richardson@intel.com>

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

_Compilation OK_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tue,  7 Feb 2023 15:22:00 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00

123296 --> 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:[~2023-02-07 15:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230207152200.122227-1-bruce.richardson@intel.com>
2023-02-07 15:17 ` qemudev [this message]
2023-02-07 15:21 ` qemudev
2023-02-07 15:24 ` |WARNING| " checkpatch
2023-02-07 18:59 ` |SUCCESS| " 0-day Robot
2023-02-07 15:56 dpdklab
2023-02-07 15:58 dpdklab
2023-02-07 16:01 dpdklab
2023-02-07 16:02 dpdklab
2023-02-07 16:05 dpdklab
2023-02-07 16:13 dpdklab
2023-02-07 16:13 dpdklab
2023-02-07 16:18 dpdklab
2023-02-07 16:19 dpdklab
2023-02-07 16:22 dpdklab
2023-02-07 16:29 dpdklab
2023-02-07 17:58 dpdklab
2023-02-08  9:45 dpdklab
2023-02-08 10:29 dpdklab
2023-02-08 11:26 dpdklab
2023-02-08 11:26 dpdklab
2023-02-08 11:26 dpdklab
2023-02-08 11:26 dpdklab
2023-02-08 11:27 dpdklab
2023-02-08 11:27 dpdklab
2023-02-08 11:27 dpdklab
2023-02-08 18:58 dpdklab
2023-02-08 21:31 dpdklab
2023-02-09  2:31 dpdklab
2023-02-09 11:57 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=202302071517.317FH1PA799782@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).