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| pw143215-143218 [PATCH] [v3,4/4] usertools/dpdk-devbind: p
Date: Tue, 20 Aug 2024 10:05:21 -0700 (PDT)	[thread overview]
Message-ID: <66c4ccd1.050a0220.ee106.e6a2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <eac66a44f1ec333c04fa44010d34c7730e1d9432.1724168117.git.anatoly.burakov@intel.com>

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

_Testing PASS_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Tuesday, August 20 2024 15:35:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c

143215-143218 --> testing pass

Upstream job id: Generic-Unit-Test-DPDK#253569

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 38 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Fedora 40           | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PASS           |
+---------------------+----------------+
| RHEL9               | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Ubuntu 24.04        | PASS           |
+---------------------+----------------+


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

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Debian Bullseye
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-20 17:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <eac66a44f1ec333c04fa44010d34c7730e1d9432.1724168117.git.anatoly.burakov@intel.com>
2024-08-20 15:11 ` |SUCCESS| pw143215-143218 [PATCH v3 4/4] usertools/dpdk-devbind: print NUMA node qemudev
2024-08-20 15:15 ` qemudev
2024-08-20 15:37 ` |SUCCESS| pw143218 " checkpatch
2024-08-20 16:06 ` |PENDING| pw143215-143218 [PATCH] [v3,4/4] usertools/dpdk-devbind: p dpdklab
2024-08-20 16:07 ` dpdklab
2024-08-20 16:11 ` |SUCCESS| " dpdklab
2024-08-20 16:25 ` dpdklab
2024-08-20 16:29 ` dpdklab
2024-08-20 16:29 ` dpdklab
2024-08-20 16:30 ` dpdklab
2024-08-20 16:42 ` dpdklab
2024-08-20 16:42 ` dpdklab
2024-08-20 16:43 ` dpdklab
2024-08-20 16:44 ` dpdklab
2024-08-20 16:45 ` dpdklab
2024-08-20 16:45 ` dpdklab
2024-08-20 16:45 ` dpdklab
2024-08-20 16:47 ` dpdklab
2024-08-20 16:52 ` dpdklab
2024-08-20 17:05 ` dpdklab
2024-08-20 17:05 ` dpdklab [this message]
2024-08-20 17:31 ` dpdklab
2024-08-20 17:47 ` dpdklab
2024-08-20 17:52 ` dpdklab
2024-08-20 18:22 ` |SUCCESS| pw143218 [PATCH v3 4/4] usertools/dpdk-devbind: print NUMA node 0-day Robot

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=66c4ccd1.050a0220.ee106.e6a2SMTPIN_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).