automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126125-126137 [PATCH v6 15/15] eal: do not define typeof macro when building with MSVC
Date: Sat, 15 Apr 2023 09:07:37 +0800	[thread overview]
Message-ID: <202304150107.33F17bvi2464993@localhost.localdomain> (raw)
In-Reply-To: <1681521346-20356-16-git-send-email-roretzla@linux.microsoft.com>

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

_Compilation OK_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Fri, 14 Apr 2023 18:15:32 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd

126125-126137 --> 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-04-15  1:21 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1681521346-20356-16-git-send-email-roretzla@linux.microsoft.com>
2023-04-15  1:07 ` qemudev [this message]
2023-04-15  1:11 ` qemudev
2023-04-15  1:18 ` |SUCCESS| pw126137 " checkpatch
2023-04-15  2:39 ` 0-day Robot
2023-04-15  2:31 |SUCCESS| pw126125-126137 [PATCH] [v6, " dpdklab
2023-04-15  2:34 dpdklab
2023-04-15  2:38 dpdklab
2023-04-15  2:39 dpdklab
2023-04-15  2:39 dpdklab
2023-04-15  2:44 dpdklab
2023-04-15  2:47 dpdklab
2023-04-15  2:49 dpdklab
2023-04-15  2:56 dpdklab
2023-04-15  3:05 dpdklab
2023-04-15  3:12 dpdklab
2023-04-15  3:13 dpdklab
2023-04-15  3:17 dpdklab
2023-04-15  3:17 dpdklab
2023-04-15  3:18 dpdklab
2023-04-15  3:19 dpdklab
2023-04-15  3:21 dpdklab
2023-04-15  3:26 dpdklab
2023-04-15  3:33 dpdklab
2023-04-15  3:37 dpdklab
2023-04-15  3:45 dpdklab
2023-04-15  3:46 dpdklab
2023-04-15  3:50 dpdklab
2023-04-15  3:50 dpdklab
2023-04-15  3:57 dpdklab
2023-04-15  3:58 dpdklab
2023-04-15  3:59 dpdklab
2023-04-15  4:02 dpdklab
2023-04-15  4:05 dpdklab
2023-04-15  4:06 dpdklab
2023-04-15  4:07 dpdklab
2023-04-15  4:07 dpdklab
2023-04-15  4:20 dpdklab
2023-04-15  4:31 dpdklab
2023-04-15  4:33 dpdklab
2023-04-15  4:41 dpdklab
2023-04-15  4:44 dpdklab
2023-04-15  4:45 dpdklab
2023-04-15  4:54 dpdklab
2023-04-15  4:59 dpdklab
2023-04-15  4:59 dpdklab
2023-04-15  5:06 dpdklab
2023-04-15  6:05 dpdklab
2023-04-15  7:57 dpdklab
2023-04-15  8:02 dpdklab
2023-04-15  8:18 dpdklab
2023-04-15  8:22 dpdklab
2023-04-15  8:39 dpdklab
2023-04-15  8:42 dpdklab
2023-04-15  9:41 dpdklab
2023-04-15  9:51 dpdklab
2023-04-15 10:17 dpdklab
2023-04-15 10:59 dpdklab
2023-04-15 13:24 dpdklab
2023-04-15 13:24 dpdklab
2023-04-15 13:54 dpdklab
2023-04-15 13:54 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=202304150107.33F17bvi2464993@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).