automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw146202-146203 [PATCH 2/2] gpudev: add malloc annotations to rte_gpu_mem_alloc
Date: Fri, 18 Oct 2024 06:31:17 +0800	[thread overview]
Message-ID: <202410172231.49HMVHnk2934947@localhost.localdomain> (raw)
In-Reply-To: <20241017225844.235401-3-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 17 Oct 2024 15:58:03 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: fe8eba692c59a92c9308f1fe429b101b9f2377bf

146202-146203 --> 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-10-17 23:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241017225844.235401-3-stephen@networkplumber.org>
2024-10-17 22:31 ` qemudev [this message]
2024-10-17 22:35 ` qemudev
2024-10-17 23:00 ` |SUCCESS| pw146203 " checkpatch
2024-10-18  0:02 ` |FAILURE| " 0-day Robot
2024-10-18 11:58 ` |SUCCESS| pw146202-146203 [PATCH] [2/2] gpudev: add malloc annotatio dpdklab
2024-10-18 12:12 ` dpdklab
2024-10-18 12:18 ` dpdklab
2024-10-18 12:23 ` dpdklab
2024-10-18 21:40 ` dpdklab
2024-10-19  0:59 ` |FAILURE| " dpdklab
2024-10-19  1:04 ` dpdklab
2024-10-19  1:05 ` dpdklab
2024-10-19  1:58 ` |PENDING| " dpdklab
2024-10-19  5:33 ` |FAILURE| " dpdklab
2024-10-19  5:50 ` dpdklab
2024-10-19  5:53 ` dpdklab
2024-10-19  6:28 ` dpdklab
2024-10-19  7:42 ` dpdklab
2024-10-19  7:43 ` dpdklab
2024-10-19  7:44 ` dpdklab
2024-10-21 23:50 ` |WARNING| " dpdklab
2024-10-23  8:10 ` |FAILURE| " 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=202410172231.49HMVHnk2934947@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).