automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138576 [PATCH] eal: mark rte_exit as cold
Date: Thu, 21 Mar 2024 00:42:59 +0800	[thread overview]
Message-ID: <202403201642.42KGgxs13935162@localhost.localdomain> (raw)
In-Reply-To: <20240320170522.122517-1-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed, 20 Mar 2024 10:05:22 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138576 --> 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 17:07 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240320170522.122517-1-stephen@networkplumber.org>
2024-03-20 16:42 ` qemudev [this message]
2024-03-20 16:47 ` qemudev
2024-03-20 17:07 ` checkpatch
2024-03-20 18:04 ` |FAILURE| " 0-day Robot
2024-03-20 18:51 ` |SUCCESS| " dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:53 ` dpdklab
2024-03-20 18:54 ` dpdklab
2024-03-20 18:55 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:56 ` dpdklab
2024-03-20 18:57 ` dpdklab
2024-03-20 18:58 ` dpdklab
2024-03-20 18:58 ` dpdklab
2024-03-20 18:58 ` dpdklab
2024-03-20 18:59 ` dpdklab
2024-03-20 19:00 ` dpdklab
2024-03-20 19:00 ` dpdklab
2024-03-20 19:01 ` dpdklab
2024-03-20 19:04 ` dpdklab
2024-03-20 19:09 ` dpdklab
2024-03-20 19:14 ` dpdklab
2024-03-20 19:15 ` dpdklab
2024-03-20 19:18 ` dpdklab
2024-03-20 19:18 ` dpdklab
2024-03-20 19:19 ` dpdklab
2024-03-20 19:19 ` dpdklab
2024-03-20 19:19 ` dpdklab
2024-03-20 19:20 ` dpdklab
2024-03-20 19:20 ` dpdklab
2024-03-20 19:20 ` dpdklab
2024-03-20 19:21 ` dpdklab
2024-03-20 19:21 ` dpdklab
2024-03-20 19:21 ` dpdklab
2024-03-20 19:22 ` dpdklab
2024-03-20 19:28 ` dpdklab
2024-03-20 19:30 ` dpdklab
2024-03-20 19:31 ` dpdklab
2024-03-20 19:31 ` dpdklab
2024-03-20 19:32 ` dpdklab
2024-03-20 19:38 ` dpdklab
2024-03-20 19:38 ` dpdklab
2024-03-20 19:38 ` dpdklab
2024-03-20 19:38 ` dpdklab
2024-03-20 19:38 ` dpdklab
2024-03-20 19:39 ` dpdklab
2024-03-20 19:39 ` dpdklab
2024-03-20 19:39 ` dpdklab
2024-03-20 19:39 ` dpdklab
2024-03-20 19:39 ` dpdklab
2024-03-20 19:41 ` dpdklab
2024-03-20 19:46 ` dpdklab
2024-03-20 19:46 ` dpdklab
2024-03-20 19:49 ` dpdklab
2024-03-20 19:49 ` dpdklab
2024-03-20 19:50 ` dpdklab
2024-03-20 19:50 ` dpdklab
2024-03-20 19:51 ` dpdklab
2024-03-20 19:51 ` dpdklab
2024-03-20 19:57 ` dpdklab
2024-03-20 20:02 ` dpdklab
2024-03-20 20:02 ` dpdklab
2024-03-20 20:03 ` dpdklab
2024-03-20 20:05 ` dpdklab
2024-03-20 20:08 ` dpdklab
2024-03-20 20:09 ` dpdklab
2024-03-20 20:24 ` dpdklab
2024-03-20 20:28 ` dpdklab
2024-03-20 20:29 ` dpdklab
2024-03-20 20:33 ` dpdklab
2024-03-20 20:51 ` dpdklab
2024-03-20 21:00 ` dpdklab
2024-03-20 22:56 ` dpdklab
2024-03-20 23:23 ` dpdklab
2024-03-20 23:24 ` dpdklab
2024-03-20 23:41 ` dpdklab
2024-03-21 13:54 ` dpdklab
2024-03-22  8:26 ` dpdklab
2024-03-22  8:42 ` 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=202403201642.42KGgxs13935162@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).