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| pw140285 [PATCH] [v3] net/af_xdp: fix umem map size for ze
Date: Thu, 23 May 2024 05:31:59 -0700 (PDT)	[thread overview]
Message-ID: <664f373f.170a0220.5fe27.2ff5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240523065302.2345392-1-frank.du@intel.com>

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140285

_Testing PASS_

Submitter: Frank Du <frank.du@intel.com>
Date: Thursday, May 23 2024 06:53:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a012926d36f3feb9d17a51c8f1559f466570ec0a

140285 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+


CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

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

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

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-23 12:32 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240523065302.2345392-1-frank.du@intel.com>
2024-05-23  6:44 ` |SUCCESS| pw140285 [PATCH v3] net/af_xdp: fix umem map size for zero copy qemudev
2024-05-23  6:49 ` qemudev
2024-05-23  7:12 ` |WARNING| " checkpatch
2024-05-23  8:04 ` |SUCCESS| " 0-day Robot
2024-05-23 10:42 ` |SUCCESS| pw140285 [PATCH] [v3] net/af_xdp: fix umem map size for ze dpdklab
2024-05-23 10:44 ` dpdklab
2024-05-23 10:46 ` dpdklab
2024-05-23 10:46 ` dpdklab
2024-05-23 10:46 ` dpdklab
2024-05-23 10:47 ` dpdklab
2024-05-23 10:48 ` dpdklab
2024-05-23 10:49 ` dpdklab
2024-05-23 10:49 ` dpdklab
2024-05-23 10:50 ` dpdklab
2024-05-23 10:50 ` dpdklab
2024-05-23 10:50 ` dpdklab
2024-05-23 11:05 ` dpdklab
2024-05-23 11:05 ` dpdklab
2024-05-23 11:06 ` dpdklab
2024-05-23 11:06 ` dpdklab
2024-05-23 11:06 ` dpdklab
2024-05-23 11:07 ` dpdklab
2024-05-23 11:07 ` dpdklab
2024-05-23 11:08 ` dpdklab
2024-05-23 11:10 ` dpdklab
2024-05-23 11:10 ` dpdklab
2024-05-23 11:11 ` dpdklab
2024-05-23 11:11 ` dpdklab
2024-05-23 11:11 ` dpdklab
2024-05-23 11:11 ` dpdklab
2024-05-23 11:19 ` dpdklab
2024-05-23 11:29 ` dpdklab
2024-05-23 11:30 ` dpdklab
2024-05-23 11:33 ` dpdklab
2024-05-23 11:34 ` dpdklab
2024-05-23 11:36 ` dpdklab
2024-05-23 11:41 ` dpdklab
2024-05-23 11:44 ` dpdklab
2024-05-23 11:44 ` dpdklab
2024-05-23 11:45 ` dpdklab
2024-05-23 11:48 ` dpdklab
2024-05-23 11:55 ` dpdklab
2024-05-23 12:07 ` dpdklab
2024-05-23 12:07 ` dpdklab
2024-05-23 12:08 ` dpdklab
2024-05-23 12:08 ` dpdklab
2024-05-23 12:09 ` dpdklab
2024-05-23 12:10 ` dpdklab
2024-05-23 12:10 ` dpdklab
2024-05-23 12:11 ` dpdklab
2024-05-23 12:12 ` dpdklab
2024-05-23 12:20 ` dpdklab
2024-05-23 12:20 ` dpdklab
2024-05-23 12:21 ` dpdklab
2024-05-23 12:21 ` dpdklab
2024-05-23 12:22 ` dpdklab
2024-05-23 12:23 ` dpdklab
2024-05-23 12:23 ` dpdklab
2024-05-23 12:23 ` dpdklab
2024-05-23 12:23 ` dpdklab
2024-05-23 12:25 ` dpdklab
2024-05-23 12:27 ` dpdklab
2024-05-23 12:27 ` dpdklab
2024-05-23 12:27 ` dpdklab
2024-05-23 12:29 ` dpdklab
2024-05-23 12:29 ` dpdklab
2024-05-23 12:30 ` dpdklab
2024-05-23 12:30 ` dpdklab
2024-05-23 12:30 ` dpdklab
2024-05-23 12:30 ` dpdklab
2024-05-23 12:30 ` dpdklab
2024-05-23 12:31 ` dpdklab
2024-05-23 12:31 ` dpdklab
2024-05-23 12:31 ` dpdklab [this message]
2024-05-23 12:32 ` dpdklab
2024-05-23 12:32 ` dpdklab
2024-05-23 12:32 ` dpdklab
2024-05-23 12:33 ` dpdklab
2024-05-23 12:35 ` dpdklab
2024-05-23 12:44 ` dpdklab
2024-05-23 12:47 ` dpdklab
2024-05-23 12:53 ` dpdklab
2024-05-23 12:54 ` dpdklab
2024-05-23 12:55 ` dpdklab
2024-05-23 12:55 ` dpdklab
2024-05-23 12:56 ` dpdklab
2024-05-23 12:58 ` dpdklab
2024-05-23 13:01 ` dpdklab
2024-05-23 13:27 ` dpdklab
2024-05-23 13:45 ` dpdklab
2024-05-23 13:54 ` 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=664f373f.170a0220.5fe27.2ff5SMTPIN_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).