automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148943 [PATCH dpdk] log: fix double free on cleanup
Date: Fri, 29 Nov 2024 23:39:13 +0800	[thread overview]
Message-ID: <202411291539.4ATFdDk83850032@localhost.localdomain> (raw)
In-Reply-To: <20241129161013.704859-2-rjarry@redhat.com>

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

_Compilation OK_

Submitter: Robin Jarry <rjarry@redhat.com>
Date: Fri, 29 Nov 2024 17:10:14 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: c0f5a9dd74f41688660e4ef84487a175ee44a54a

148943 --> 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-11-29 16:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241129161013.704859-2-rjarry@redhat.com>
2024-11-29 15:39 ` qemudev [this message]
2024-11-29 15:43 ` qemudev
2024-11-29 16:11 ` checkpatch
2024-11-29 17:23 ` 0-day Robot
2024-11-29 18:34 ` |SUCCESS| pw148943 [PATCH] " dpdklab
2024-11-29 19:20 ` dpdklab
2024-11-29 19:40 ` dpdklab
2024-11-29 19:41 ` dpdklab
2024-11-29 19:48 ` dpdklab
2024-11-29 19:50 ` dpdklab
2024-11-29 19:54 ` dpdklab
2024-11-29 19:59 ` dpdklab
2024-11-29 20:00 ` dpdklab
2024-11-29 20:01 ` dpdklab
2024-11-29 20:08 ` |PENDING| " dpdklab
2024-11-29 20:13 ` dpdklab
2024-11-29 20:29 ` |SUCCESS| " dpdklab
2024-11-29 20:46 ` dpdklab
2024-11-29 20:52 ` dpdklab
2024-11-29 20:53 ` dpdklab
2024-11-29 21:12 ` |WARNING| " dpdklab
2024-11-29 21:17 ` dpdklab
2024-11-29 21:56 ` |SUCCESS| " dpdklab
2024-11-29 22:00 ` 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=202411291539.4ATFdDk83850032@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).