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| pw134880 [PATCH] [v2] net/af_xdp: fix memzone leak in erro
Date: Tue, 05 Dec 2023 07:42:43 -0800 (PST)	[thread overview]
Message-ID: <656f44f3.d40a0220.85a27.d269SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134880

_Testing PASS_

Submitter: wangyunjian <wangyunjian@huawei.com>
Date: Tuesday, December 05 2023 12:23:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a526461b0764de52b09b073df84f9e87ec120c93

134880 --> testing pass

Test environment and result as below:

+---------------------+--------------------+
|     Environment     | dpdk_meson_compile |
+=====================+====================+
| Windows Server 2022 | PASS               |
+---------------------+--------------------+
| CentOS Stream 8     | PASS               |
+---------------------+--------------------+
| Debian Bullseye     | PASS               |
+---------------------+--------------------+
| FreeBSD 13          | PASS               |
+---------------------+--------------------+
| Debian Buster       | PASS               |
+---------------------+--------------------+
| Fedora 38           | PASS               |
+---------------------+--------------------+
| CentOS Stream 9     | PASS               |
+---------------------+--------------------+
| Fedora 37           | PASS               |
+---------------------+--------------------+
| Ubuntu 22.04        | PASS               |
+---------------------+--------------------+
| Ubuntu 20.04        | PASS               |
+---------------------+--------------------+
| openSUSE Leap 15    | PASS               |
+---------------------+--------------------+
| RHEL8               | PASS               |
+---------------------+--------------------+
| Alpine              | PASS               |
+---------------------+--------------------+


Windows Server 2022
	Kernel: OS Build 20348.2031
	Compiler: MSVC VS-Preview

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-05 15:42 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 15:42 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-05 22:07 dpdklab
2023-12-05 21:02 dpdklab
2023-12-05 20:54 dpdklab
2023-12-05 20:53 dpdklab
2023-12-05 20:52 dpdklab
2023-12-05 20:51 dpdklab
2023-12-05 20:49 dpdklab
2023-12-05 20:48 dpdklab
2023-12-05 20:47 dpdklab
2023-12-05 20:47 dpdklab
2023-12-05 20:46 dpdklab
2023-12-05 20:45 dpdklab
2023-12-05 20:45 dpdklab
2023-12-05 20:45 dpdklab
2023-12-05 20:44 dpdklab
2023-12-05 20:43 dpdklab
2023-12-05 20:43 dpdklab
2023-12-05 20:42 dpdklab
2023-12-05 20:42 dpdklab
2023-12-05 20:42 dpdklab
2023-12-05 20:42 dpdklab
2023-12-05 20:42 dpdklab
2023-12-05 20:41 dpdklab
2023-12-05 20:41 dpdklab
2023-12-05 20:40 dpdklab
2023-12-05 20:39 dpdklab
2023-12-05 20:39 dpdklab
2023-12-05 20:39 dpdklab
2023-12-05 20:39 dpdklab
2023-12-05 20:38 dpdklab
2023-12-05 20:37 dpdklab
2023-12-05 20:36 dpdklab
2023-12-05 20:31 dpdklab
2023-12-05 20:29 dpdklab
2023-12-05 20:26 dpdklab
2023-12-05 20:21 dpdklab
2023-12-05 20:16 dpdklab
2023-12-05 20:12 dpdklab
2023-12-05 18:17 dpdklab
2023-12-05 17:11 dpdklab
2023-12-05 16:22 dpdklab
2023-12-05 16:20 dpdklab
2023-12-05 16:17 dpdklab
2023-12-05 16:10 dpdklab
2023-12-05 16:09 dpdklab
2023-12-05 15:59 dpdklab
2023-12-05 15:59 dpdklab
2023-12-05 15:58 dpdklab
2023-12-05 15:57 dpdklab
2023-12-05 15:57 dpdklab
2023-12-05 15:57 dpdklab
2023-12-05 15:57 dpdklab
2023-12-05 15:56 dpdklab
2023-12-05 15:56 dpdklab
2023-12-05 15:56 dpdklab
2023-12-05 15:55 dpdklab
2023-12-05 15:55 dpdklab
2023-12-05 15:55 dpdklab
2023-12-05 15:55 dpdklab
2023-12-05 15:55 dpdklab
2023-12-05 15:55 dpdklab
2023-12-05 15:55 dpdklab
2023-12-05 15:55 dpdklab
2023-12-05 15:55 dpdklab
2023-12-05 15:54 dpdklab
2023-12-05 15:52 dpdklab
2023-12-05 15:52 dpdklab
2023-12-05 15:51 dpdklab
2023-12-05 15:51 dpdklab
2023-12-05 15:51 dpdklab
2023-12-05 15:49 dpdklab
2023-12-05 15:48 dpdklab
2023-12-05 15:48 dpdklab
2023-12-05 15:48 dpdklab
2023-12-05 15:47 dpdklab
2023-12-05 15:47 dpdklab
2023-12-05 15:47 dpdklab
2023-12-05 15:47 dpdklab
2023-12-05 15:47 dpdklab
2023-12-05 15:47 dpdklab
2023-12-05 15:46 dpdklab
2023-12-05 15:46 dpdklab
2023-12-05 15:45 dpdklab
2023-12-05 15:45 dpdklab
2023-12-05 15:45 dpdklab
2023-12-05 15:44 dpdklab
2023-12-05 15:43 dpdklab
2023-12-05 15:43 dpdklab
2023-12-05 15:43 dpdklab
2023-12-05 15:42 dpdklab
2023-12-05 15: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=656f44f3.d40a0220.85a27.d269SMTPIN_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).