automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140138 [PATCH v5] devtools: add .clang-format file
Date: Thu, 16 May 2024 16:01:08 +0800	[thread overview]
Message-ID: <202405160801.44G818ZH002579@localhost.localdomain> (raw)
In-Reply-To: <20240516082051.1255621-1-aomeryamac@gmail.com>

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

_Compilation OK_

Submitter: Abdullah Ömer Yamaç <aomeryamac@gmail.com>
Date: Thu, 16 May 2024 08:20:51 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

140138 --> 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-05-16  8:29 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240516082051.1255621-1-aomeryamac@gmail.com>
2024-05-16  8:01 ` qemudev [this message]
2024-05-16  8:05 ` qemudev
2024-05-16  8:21 ` checkpatch
2024-05-16  9:02 ` |SUCCESS| pw140138 [PATCH] [v5] " dpdklab
2024-05-16  9:03 ` dpdklab
2024-05-16  9:03 ` dpdklab
2024-05-16  9:04 ` dpdklab
2024-05-16  9:05 ` dpdklab
2024-05-16  9:06 ` dpdklab
2024-05-16  9:06 ` dpdklab
2024-05-16  9:11 ` dpdklab
2024-05-16  9:12 ` dpdklab
2024-05-16  9:12 ` dpdklab
2024-05-16  9:12 ` dpdklab
2024-05-16  9:13 ` dpdklab
2024-05-16  9:13 ` dpdklab
2024-05-16  9:13 ` dpdklab
2024-05-16  9:13 ` dpdklab
2024-05-16  9:13 ` dpdklab
2024-05-16  9:14 ` dpdklab
2024-05-16  9:14 ` dpdklab
2024-05-16  9:14 ` dpdklab
2024-05-16  9:14 ` dpdklab
2024-05-16  9:14 ` dpdklab
2024-05-16  9:14 ` dpdklab
2024-05-16  9:14 ` dpdklab
2024-05-16  9:15 ` dpdklab
2024-05-16  9:15 ` dpdklab
2024-05-16  9:15 ` dpdklab
2024-05-16  9:15 ` dpdklab
2024-05-16  9:15 ` dpdklab
2024-05-16  9:16 ` dpdklab
2024-05-16  9:16 ` dpdklab
2024-05-16  9:19 ` dpdklab
2024-05-16  9:19 ` dpdklab
2024-05-16  9:19 ` dpdklab
2024-05-16  9:20 ` dpdklab
2024-05-16  9:20 ` dpdklab
2024-05-16  9:20 ` dpdklab
2024-05-16  9:20 ` dpdklab
2024-05-16  9:20 ` dpdklab
2024-05-16  9:20 ` dpdklab
2024-05-16  9:21 ` dpdklab
2024-05-16  9:21 ` dpdklab
2024-05-16  9:21 ` dpdklab
2024-05-16  9:22 ` dpdklab
2024-05-16  9:22 ` dpdklab
2024-05-16  9:22 ` dpdklab
2024-05-16  9:22 ` dpdklab
2024-05-16  9:22 ` dpdklab
2024-05-16  9:22 ` dpdklab
2024-05-16  9:23 ` dpdklab
2024-05-16  9:23 ` dpdklab
2024-05-16  9:23 ` dpdklab
2024-05-16  9:24 ` dpdklab
2024-05-16  9:24 ` |SUCCESS| pw140138 [PATCH v5] " 0-day Robot
2024-05-16  9:25 ` |SUCCESS| pw140138 [PATCH] [v5] " dpdklab
2024-05-16  9:26 ` dpdklab
2024-05-16  9:26 ` dpdklab
2024-05-16  9:26 ` dpdklab
2024-05-16  9:26 ` dpdklab
2024-05-16  9:27 ` dpdklab
2024-05-16  9:27 ` dpdklab
2024-05-16  9:27 ` dpdklab
2024-05-16  9:28 ` dpdklab
2024-05-16  9:28 ` dpdklab
2024-05-16  9:28 ` dpdklab
2024-05-16  9:28 ` dpdklab
2024-05-16  9:29 ` dpdklab
2024-05-16  9:36 ` |FAILURE| " dpdklab
2024-05-16  9:40 ` |SUCCESS| " dpdklab
2024-05-16  9:46 ` dpdklab
2024-05-16  9:47 ` |FAILURE| " dpdklab
2024-05-16  9:47 ` |SUCCESS| " dpdklab
2024-05-16  9:47 ` |FAILURE| " dpdklab
2024-05-16  9:47 ` |SUCCESS| " dpdklab
2024-05-16  9:48 ` |FAILURE| " dpdklab
2024-05-16  9:48 ` dpdklab
2024-05-16  9:50 ` |SUCCESS| " dpdklab
2024-05-16  9:51 ` |FAILURE| " dpdklab
2024-05-16  9:51 ` |SUCCESS| " dpdklab
2024-05-16  9:52 ` dpdklab
2024-05-16  9:53 ` |FAILURE| " dpdklab
2024-05-16  9:56 ` dpdklab
2024-05-16  9:58 ` |SUCCESS| " dpdklab
2024-05-16  9:59 ` dpdklab
2024-05-16  9:59 ` dpdklab
2024-05-16 10:01 ` dpdklab
2024-05-16 10:15 ` dpdklab
2024-05-16 10:17 ` 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=202405160801.44G818ZH002579@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).