automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw142136 [PATCH v3] buildtools: fix invalid symbols
Date: Fri, 5 Jul 2024 20:09:27 +0800	[thread overview]
Message-ID: <202407051209.465C9Rrc1045874@localhost.localdomain> (raw)
In-Reply-To: <20240705082550.1670765-1-mingjinx.ye@intel.com>

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

_Compilation OK_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Fri,  5 Jul 2024 08:25:50 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: a5d4e2461cb3b038fa287ad7b999ba86eabbcff3

142136 --> 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:[~2024-07-05 12:38 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240705082550.1670765-1-mingjinx.ye@intel.com>
2024-07-05  8:49 ` checkpatch
2024-07-05  9:43 ` 0-day Robot
2024-07-05 12:09 ` qemudev [this message]
2024-07-05 12:14 ` qemudev
2024-07-06  2:00 ` |PENDING| pw142136 [PATCH] [v3] " dpdklab
2024-07-06  2:12 ` |SUCCESS| " dpdklab
2024-07-06  2:14 ` dpdklab
2024-07-06  2:20 ` dpdklab
2024-07-06  2:34 ` dpdklab
2024-07-06  2:35 ` |PENDING| " dpdklab
2024-07-06  2:36 ` dpdklab
2024-07-06  2:46 ` dpdklab
2024-07-06  2:53 ` |SUCCESS| " dpdklab
2024-07-06  2:53 ` |PENDING| " dpdklab
2024-07-06  2:58 ` dpdklab
2024-07-06  3:01 ` dpdklab
2024-07-06  3:04 ` dpdklab
2024-07-06  3:04 ` dpdklab
2024-07-06  3:07 ` dpdklab
2024-07-06  3:09 ` dpdklab
2024-07-06  3:14 ` dpdklab
2024-07-06  3:18 ` dpdklab
2024-07-06  3:20 ` dpdklab
2024-07-06  3:29 ` |SUCCESS| " dpdklab
2024-07-06  3:30 ` dpdklab
2024-07-06  4:05 ` dpdklab
2024-07-06  4:08 ` dpdklab
2024-07-06  4:10 ` dpdklab
2024-07-06  4:14 ` dpdklab
2024-07-06  4:16 ` dpdklab
2024-07-06  4:19 ` dpdklab
2024-07-06  4:39 ` dpdklab
2024-07-06  4:50 ` dpdklab
2024-07-06  9:26 ` |PENDING| " dpdklab
2024-07-06  9:27 ` dpdklab
2024-07-06  9:30 ` dpdklab
2024-07-06  9:32 ` dpdklab
2024-07-06  9:37 ` dpdklab
2024-07-06  9:40 ` |SUCCESS| " dpdklab
2024-07-06  9:41 ` dpdklab
2024-07-06 10:12 ` |PENDING| " dpdklab
2024-07-06 11:05 ` dpdklab
2024-07-06 12:11 ` dpdklab
2024-07-06 12:12 ` dpdklab
2024-07-06 12:16 ` dpdklab
2024-07-06 12:16 ` dpdklab
2024-07-06 12:19 ` dpdklab
2024-07-06 12:27 ` dpdklab
2024-07-06 12:28 ` dpdklab
2024-07-06 12:29 ` dpdklab
2024-07-06 12:31 ` dpdklab
2024-07-06 12:32 ` dpdklab
2024-07-06 12:35 ` dpdklab
2024-07-06 12:36 ` dpdklab
2024-07-06 12:38 ` dpdklab
2024-07-06 12:39 ` dpdklab
2024-07-06 13:45 ` |SUCCESS| " dpdklab
2024-07-06 20:41 ` |PENDING| " dpdklab
2024-07-06 21:16 ` dpdklab
2024-07-06 21:17 ` dpdklab
2024-07-06 21:20 ` dpdklab
2024-07-06 21:22 ` dpdklab
2024-07-06 21:24 ` dpdklab
2024-07-06 21:27 ` dpdklab
2024-07-06 21:27 ` dpdklab
2024-07-06 21:29 ` dpdklab
2024-07-06 21:29 ` dpdklab
2024-07-06 21:30 ` dpdklab
2024-07-06 21:31 ` dpdklab
2024-07-06 21:33 ` dpdklab
2024-07-06 21:34 ` dpdklab
2024-07-06 21:34 ` dpdklab
2024-07-06 21:34 ` dpdklab
2024-07-06 21:35 ` dpdklab
2024-07-06 21:42 ` dpdklab
2024-07-06 21:42 ` dpdklab
2024-07-06 21:44 ` |SUCCESS| " dpdklab
2024-07-06 21:47 ` |PENDING| " dpdklab
2024-07-06 21:54 ` |SUCCESS| " dpdklab
2024-07-06 22:51 ` |PENDING| " dpdklab
2024-07-06 23:03 ` |SUCCESS| " dpdklab
2024-07-09  3:19 ` dpdklab
2024-07-09  3:33 ` 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=202407051209.465C9Rrc1045874@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).