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| pw138486 [PATCH] [v3] app/dma-perf: calrify incorrect NUMA
Date: Tue, 19 Mar 2024 19:27:41 -0700 (PDT)	[thread overview]
Message-ID: <65fa499d.050a0220.68f6c.1437SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240320014053.1040-1-vipin.varghese@amd.com>

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

_Testing PASS_

Submitter: Vipin Varghese <vipin.varghese@amd.com>
Date: Wednesday, March 20 2024 01:40:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138486 --> testing pass

Test environment and result as below:

+---------------------+-------------------+--------------------+----------------------+
|     Environment     | dpdk_msvc_compile | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+===================+====================+======================+
| Windows Server 2022 | PASS              | PASS               | PASS                 |
+---------------------+-------------------+--------------------+----------------------+
| Debian 11 (arm)     | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| FreeBSD 13.2        | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Debian Bullseye     | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| CentOS Stream 8     | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| CentOS Stream 9     | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Fedora 37           | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Windows Server 2019 | SKIPPED           | PASS               | PASS                 |
+---------------------+-------------------+--------------------+----------------------+
| RHEL8               | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Fedora 38           | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Ubuntu 20.04        | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| openSUSE Leap 15    | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Alpine              | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+
| Ubuntu 22.04        | SKIPPED           | PASS               | SKIPPED              |
+---------------------+-------------------+--------------------+----------------------+


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

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

FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 14.0.5

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

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

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

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

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

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

Fedora 38
	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

Alpine
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924

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

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

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-20  2:27 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240320014053.1040-1-vipin.varghese@amd.com>
2024-03-20  1:19 ` |SUCCESS| pw138486 [PATCH v3] app/dma-perf: calrify incorrect NUMA config qemudev
2024-03-20  1:23 ` qemudev
2024-03-20  1:43 ` checkpatch
2024-03-20  2:27 ` dpdklab [this message]
2024-03-20  2:28 ` |SUCCESS| pw138486 [PATCH] [v3] app/dma-perf: calrify incorrect NUMA dpdklab
2024-03-20  2:28 ` dpdklab
2024-03-20  2:29 ` dpdklab
2024-03-20  2:29 ` dpdklab
2024-03-20  2:29 ` dpdklab
2024-03-20  2:30 ` dpdklab
2024-03-20  2:30 ` dpdklab
2024-03-20  2:30 ` dpdklab
2024-03-20  2:30 ` dpdklab
2024-03-20  2:31 ` dpdklab
2024-03-20  2:31 ` dpdklab
2024-03-20  2:32 ` dpdklab
2024-03-20  2:32 ` dpdklab
2024-03-20  2:33 ` dpdklab
2024-03-20  2:33 ` dpdklab
2024-03-20  2:33 ` dpdklab
2024-03-20  2:33 ` dpdklab
2024-03-20  2:34 ` dpdklab
2024-03-20  2:34 ` dpdklab
2024-03-20  2:34 ` dpdklab
2024-03-20  2:35 ` dpdklab
2024-03-20  2:35 ` dpdklab
2024-03-20  2:36 ` dpdklab
2024-03-20  2:36 ` dpdklab
2024-03-20  2:36 ` dpdklab
2024-03-20  2:37 ` dpdklab
2024-03-20  2:37 ` dpdklab
2024-03-20  2:37 ` dpdklab
2024-03-20  2:37 ` dpdklab
2024-03-20  2:37 ` dpdklab
2024-03-20  2:38 ` dpdklab
2024-03-20  2:38 ` dpdklab
2024-03-20  2:38 ` dpdklab
2024-03-20  2:38 ` dpdklab
2024-03-20  2:38 ` dpdklab
2024-03-20  2:38 ` dpdklab
2024-03-20  2:38 ` dpdklab
2024-03-20  2:39 ` dpdklab
2024-03-20  2:39 ` dpdklab
2024-03-20  2:39 ` dpdklab
2024-03-20  2:39 ` dpdklab
2024-03-20  2:39 ` dpdklab
2024-03-20  2:39 ` dpdklab
2024-03-20  2:39 ` dpdklab
2024-03-20  2:40 ` dpdklab
2024-03-20  2:40 ` dpdklab
2024-03-20  2:40 ` dpdklab
2024-03-20  2:40 ` dpdklab
2024-03-20  2:40 ` dpdklab
2024-03-20  2:40 ` dpdklab
2024-03-20  2:40 ` dpdklab
2024-03-20  2:40 ` dpdklab
2024-03-20  2:41 ` dpdklab
2024-03-20  2:41 ` dpdklab
2024-03-20  2:41 ` dpdklab
2024-03-20  2:41 ` dpdklab
2024-03-20  2:41 ` dpdklab
2024-03-20  2:41 ` dpdklab
2024-03-20  2:42 ` dpdklab
2024-03-20  2:42 ` dpdklab
2024-03-20  2:42 ` dpdklab
2024-03-20  2:42 ` dpdklab
2024-03-20  2:42 ` dpdklab
2024-03-20  2:43 ` dpdklab
2024-03-20  2:43 ` |SUCCESS| pw138486 [PATCH v3] app/dma-perf: calrify incorrect NUMA config 0-day Robot
2024-03-20  2:44 ` |SUCCESS| pw138486 [PATCH] [v3] app/dma-perf: calrify incorrect NUMA dpdklab
2024-03-20  2:45 ` dpdklab
2024-03-20  2:51 ` dpdklab
2024-03-20  2:53 ` dpdklab
2024-03-20  3:55 ` dpdklab
2024-03-20 20:50 ` dpdklab
2024-03-21 15:10 ` dpdklab
2024-03-21 15:47 ` 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=65fa499d.050a0220.68f6c.1437SMTPIN_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).