automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138643-138642 [PATCH 2/2] eal: adjust intrinsic type casts for CXX
Date: Thu, 21 Mar 2024 04:59:30 +0800	[thread overview]
Message-ID: <202403202059.42KKxUVs157828@localhost.localdomain> (raw)
In-Reply-To: <1710969509-20627-3-git-send-email-roretzla@linux.microsoft.com>

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

_Compilation OK_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed, 20 Mar 2024 14:18:28 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138643-138642 --> 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-03-20 21:24 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1710969509-20627-3-git-send-email-roretzla@linux.microsoft.com>
2024-03-20 20:59 ` qemudev [this message]
2024-03-20 21:04 ` qemudev
2024-03-20 21:19 ` |SUCCESS| pw138642 " checkpatch
2024-03-20 22:24 ` 0-day Robot
2024-03-21  2:25 ` |SUCCESS| pw138643-138642 [PATCH] [2/2] eal: adjust intrinsic type c dpdklab
2024-03-21  2:28 ` dpdklab
2024-03-21  2:30 ` dpdklab
2024-03-21  2:32 ` dpdklab
2024-03-21  2:33 ` dpdklab
2024-03-21  2:34 ` dpdklab
2024-03-21  2:35 ` dpdklab
2024-03-21  2:36 ` dpdklab
2024-03-21  2:36 ` dpdklab
2024-03-21  2:37 ` dpdklab
2024-03-21  2:38 ` dpdklab
2024-03-21  2:39 ` dpdklab
2024-03-21  2:57 ` dpdklab
2024-03-21  3:00 ` dpdklab
2024-03-21  3:03 ` dpdklab
2024-03-21  3:07 ` dpdklab
2024-03-21  3:42 ` dpdklab
2024-03-21  3:47 ` dpdklab
2024-03-21  4:35 ` dpdklab
2024-03-21  4:38 ` dpdklab
2024-03-21  4:38 ` dpdklab
2024-03-21  4:39 ` dpdklab
2024-03-21  4:40 ` dpdklab
2024-03-21  4:41 ` dpdklab
2024-03-21  4:43 ` dpdklab
2024-03-21  4:43 ` dpdklab
2024-03-21  4:45 ` dpdklab
2024-03-21  4:45 ` dpdklab
2024-03-21  4:50 ` dpdklab
2024-03-21  5:59 ` dpdklab
2024-03-21  6:06 ` dpdklab
2024-03-21  6:07 ` dpdklab
2024-03-21  6:08 ` dpdklab
2024-03-21  6:10 ` |FAILURE| " dpdklab
2024-03-21  6:11 ` |SUCCESS| " dpdklab
2024-03-21  6:11 ` |FAILURE| " dpdklab
2024-03-21  6:12 ` |SUCCESS| " dpdklab
2024-03-21  6:12 ` |FAILURE| " dpdklab
2024-03-21  6:12 ` |SUCCESS| " dpdklab
2024-03-21  6:13 ` dpdklab
2024-03-21  6:13 ` dpdklab
2024-03-21  6:13 ` |FAILURE| " dpdklab
2024-03-21  6:14 ` dpdklab
2024-03-21  6:15 ` dpdklab
2024-03-21  6:15 ` |SUCCESS| " dpdklab
2024-03-21  6:16 ` dpdklab
2024-03-21  6:16 ` |FAILURE| " dpdklab
2024-03-21  6:18 ` dpdklab
2024-03-21  6:19 ` dpdklab
2024-03-21  6:20 ` |SUCCESS| " dpdklab
2024-03-21  6:21 ` |FAILURE| " dpdklab
2024-03-21  6:22 ` |SUCCESS| " dpdklab
2024-03-21  6:29 ` dpdklab
2024-03-21  6:31 ` dpdklab
2024-03-21  6:32 ` dpdklab
2024-03-21  7:11 ` dpdklab
2024-03-21  7:27 ` dpdklab
2024-03-21  7:30 ` dpdklab
2024-03-21  7:32 ` dpdklab
2024-03-21  7:33 ` dpdklab
2024-03-21  7:46 ` dpdklab
2024-03-21  7:49 ` dpdklab
2024-03-21  7:55 ` dpdklab
2024-03-21  8:20 ` dpdklab
2024-03-21  8:26 ` dpdklab
2024-03-21  8:34 ` dpdklab
2024-03-21  8:45 ` dpdklab
2024-03-21  9:27 ` dpdklab
2024-03-21  9:30 ` dpdklab
2024-03-21  9:47 ` dpdklab
2024-03-21 12:36 ` |FAILURE| " dpdklab
2024-03-21 12:59 ` dpdklab
2024-03-21 18:37 ` |SUCCESS| " dpdklab
2024-03-22 21:03 ` dpdklab
2024-03-22 21:49 ` 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=202403202059.42KKxUVs157828@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).