automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138480 [PATCH] app/testpmd: fix releasing action handle
Date: Tue, 19 Mar 2024 13:40:54 -0700 (PDT)	[thread overview]
Message-ID: <65f9f856.050a0220.96108.2186SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240319093249.307606-1-bingz@nvidia.com>

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138480

_Testing PASS_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Tuesday, March 19 2024 09:32:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:53483ccd6dee01b8930e7a8c391472453bbe642d

138480 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile     | PASS               |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK                   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Fedora 37 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| Debian 12 (arm)                        | PASS               |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM)               | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                     | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM)                        | PASS               |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM)                  | PASS               |
+----------------------------------------+--------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang 10.0.0-4ubuntu1

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29593/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-03-19 20:41 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240319093249.307606-1-bingz@nvidia.com>
2024-03-19  9:09 ` |SUCCESS| pw138480 [PATCH] app/testpmd: fix releasing action handle flush memory qemudev
2024-03-19  9:14 ` qemudev
2024-03-19  9:34 ` checkpatch
2024-03-19 10:24 ` 0-day Robot
2024-03-19 18:25 ` |SUCCESS| pw138480 [PATCH] app/testpmd: fix releasing action handle dpdklab
2024-03-19 18:44 ` dpdklab
2024-03-19 18:45 ` dpdklab
2024-03-19 18:50 ` dpdklab
2024-03-19 18:57 ` dpdklab
2024-03-19 18:58 ` dpdklab
2024-03-19 18:59 ` dpdklab
2024-03-19 19:02 ` dpdklab
2024-03-19 19:30 ` dpdklab
2024-03-19 19:34 ` dpdklab
2024-03-19 19:34 ` dpdklab
2024-03-19 19:36 ` dpdklab
2024-03-19 19:39 ` dpdklab
2024-03-19 19:43 ` dpdklab
2024-03-19 19:44 ` dpdklab
2024-03-19 19:46 ` dpdklab
2024-03-19 19:47 ` dpdklab
2024-03-19 19:48 ` dpdklab
2024-03-19 19:48 ` dpdklab
2024-03-19 19:48 ` dpdklab
2024-03-19 19:50 ` dpdklab
2024-03-19 19:52 ` dpdklab
2024-03-19 20:22 ` dpdklab
2024-03-19 20:23 ` dpdklab
2024-03-19 20:31 ` dpdklab
2024-03-19 20:31 ` dpdklab
2024-03-19 20:32 ` dpdklab
2024-03-19 20:33 ` dpdklab
2024-03-19 20:33 ` dpdklab
2024-03-19 20:33 ` dpdklab
2024-03-19 20:34 ` dpdklab
2024-03-19 20:34 ` dpdklab
2024-03-19 20:36 ` dpdklab
2024-03-19 20:36 ` dpdklab
2024-03-19 20:36 ` dpdklab
2024-03-19 20:37 ` dpdklab
2024-03-19 20:37 ` dpdklab
2024-03-19 20:37 ` dpdklab
2024-03-19 20:38 ` dpdklab
2024-03-19 20:38 ` dpdklab
2024-03-19 20:38 ` dpdklab
2024-03-19 20:39 ` dpdklab
2024-03-19 20:39 ` dpdklab
2024-03-19 20:39 ` dpdklab
2024-03-19 20:39 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab
2024-03-19 20:40 ` dpdklab [this message]
2024-03-19 20:41 ` dpdklab
2024-03-19 20:41 ` dpdklab
2024-03-19 20:42 ` dpdklab
2024-03-19 20:42 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:46 ` dpdklab
2024-03-19 20:53 ` dpdklab
2024-03-19 20:54 ` dpdklab
2024-03-19 20:55 ` dpdklab
2024-03-19 20:56 ` dpdklab
2024-03-19 21:02 ` dpdklab
2024-03-19 21:03 ` dpdklab
2024-03-19 21:06 ` dpdklab
2024-03-19 21:07 ` dpdklab
2024-03-19 21:46 ` dpdklab
2024-03-19 21:59 ` dpdklab
2024-03-19 23:05 ` dpdklab
2024-03-20 18:41 ` |WARNING| " dpdklab
2024-03-21 10:37 ` |SUCCESS| " dpdklab
2024-03-21 11:16 ` 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=65f9f856.050a0220.96108.2186SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).