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| pw136796 [PATCH] [v2] net/mlx5: enable PCI related counter
Date: Wed, 14 Feb 2024 13:05:30 -0800 (PST)	[thread overview]
Message-ID: <65cd2b1a.020a0220.dd9c4.2e4aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Wathsala Vithanage <wathsala.vithanage@arm.com>
Date: Wednesday, February 14 2024 20:14:55 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:32bedd138f36b073341bbde2a5186727d1bc05d6

136796 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Buster       | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+


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

FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

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

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

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

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-14 21:05 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 21:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-14 22:15 dpdklab
2024-02-14 21:59 dpdklab
2024-02-14 21:59 dpdklab
2024-02-14 21:58 dpdklab
2024-02-14 21:58 dpdklab
2024-02-14 21:57 dpdklab
2024-02-14 21:56 dpdklab
2024-02-14 21:55 dpdklab
2024-02-14 21:53 dpdklab
2024-02-14 21:53 dpdklab
2024-02-14 21:52 dpdklab
2024-02-14 21:50 dpdklab
2024-02-14 21:48 dpdklab
2024-02-14 21:40 dpdklab
2024-02-14 21:26 dpdklab
2024-02-14 21:25 dpdklab
2024-02-14 21:25 dpdklab
2024-02-14 21:25 dpdklab
2024-02-14 21:24 dpdklab
2024-02-14 21:23 dpdklab
2024-02-14 21:22 dpdklab
2024-02-14 21:22 dpdklab
2024-02-14 21:21 dpdklab
2024-02-14 21:21 dpdklab
2024-02-14 21:20 dpdklab
2024-02-14 21:20 dpdklab
2024-02-14 21:20 dpdklab
2024-02-14 21:20 dpdklab
2024-02-14 21:19 dpdklab
2024-02-14 21:16 dpdklab
2024-02-14 21:12 dpdklab
2024-02-14 21:11 dpdklab
2024-02-14 21:11 dpdklab
2024-02-14 21:11 dpdklab
2024-02-14 21:11 dpdklab
2024-02-14 21:11 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:10 dpdklab
2024-02-14 21:09 dpdklab
2024-02-14 21:07 dpdklab
2024-02-14 21:07 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:06 dpdklab
2024-02-14 21:05 dpdklab
2024-02-14 21:05 dpdklab
2024-02-14 21:05 dpdklab
2024-02-14 21:04 dpdklab
2024-02-14 21:04 dpdklab
2024-02-14 21:04 dpdklab
2024-02-14 21:04 dpdklab
2024-02-14 21:04 dpdklab
2024-02-14 21:03 dpdklab
2024-02-14 21:03 dpdklab
2024-02-14 21:03 dpdklab
2024-02-14 21:02 dpdklab
2024-02-14 21:02 dpdklab
2024-02-14 21:02 dpdklab
2024-02-14 21:02 dpdklab
2024-02-14 21:01 dpdklab
2024-02-14 21:00 dpdklab
2024-02-14 20:59 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=65cd2b1a.020a0220.dd9c4.2e4aSMTPIN_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).