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| pw138049 [PATCH] app/dma-perf: calrify incorrect NUMA conf
Date: Wed, 06 Mar 2024 11:09:02 -0800 (PST)	[thread overview]
Message-ID: <65e8bf4e.170a0220.577a2.5b68SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240306150204.1375-1-vipin.varghese@amd.com>

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

_Testing PASS_

Submitter: Vipin Varghese <vipin.varghese@amd.com>
Date: Wednesday, March 06 2024 15:02:04 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6a9f3f6df9ef51e30ff5bf3eea00f27ffef87a16

138049 --> 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                 |
+---------------------+--------------------+----------------------+
| Debian 12 (arm)     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | 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)

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

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

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

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

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

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

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-06 19:09 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240306150204.1375-1-vipin.varghese@amd.com>
2024-03-06 14:56 ` |SUCCESS| pw138049 [PATCH] app/dma-perf: calrify incorrect NUMA config qemudev
2024-03-06 15:00 ` qemudev
2024-03-06 15:03 ` checkpatch
2024-03-06 16:04 ` 0-day Robot
2024-03-06 17:59 ` |SUCCESS| pw138049 [PATCH] app/dma-perf: calrify incorrect NUMA conf dpdklab
2024-03-06 18:02 ` dpdklab
2024-03-06 18:03 ` dpdklab
2024-03-06 18:05 ` dpdklab
2024-03-06 18:11 ` dpdklab
2024-03-06 18:12 ` dpdklab
2024-03-06 18:13 ` dpdklab
2024-03-06 18:25 ` dpdklab
2024-03-06 18:25 ` dpdklab
2024-03-06 18:25 ` dpdklab
2024-03-06 18:26 ` dpdklab
2024-03-06 18:27 ` dpdklab
2024-03-06 18:28 ` dpdklab
2024-03-06 18:28 ` dpdklab
2024-03-06 18:35 ` dpdklab
2024-03-06 18:39 ` dpdklab
2024-03-06 18:41 ` dpdklab
2024-03-06 18:42 ` dpdklab
2024-03-06 18:43 ` dpdklab
2024-03-06 18:43 ` dpdklab
2024-03-06 18:44 ` dpdklab
2024-03-06 18:44 ` dpdklab
2024-03-06 18:44 ` dpdklab
2024-03-06 18:44 ` dpdklab
2024-03-06 18:45 ` dpdklab
2024-03-06 18:46 ` dpdklab
2024-03-06 18:46 ` dpdklab
2024-03-06 18:46 ` dpdklab
2024-03-06 18:46 ` dpdklab
2024-03-06 18:52 ` dpdklab
2024-03-06 18:52 ` dpdklab
2024-03-06 18:52 ` dpdklab
2024-03-06 18:53 ` dpdklab
2024-03-06 18:54 ` dpdklab
2024-03-06 18:55 ` dpdklab
2024-03-06 18:57 ` dpdklab
2024-03-06 19:06 ` dpdklab
2024-03-06 19:06 ` dpdklab
2024-03-06 19:07 ` dpdklab
2024-03-06 19:09 ` dpdklab [this message]
2024-03-06 19:09 ` dpdklab
2024-03-06 19:11 ` dpdklab
2024-03-06 19:11 ` dpdklab
2024-03-06 19:11 ` dpdklab
2024-03-06 19:13 ` dpdklab
2024-03-06 19:13 ` dpdklab
2024-03-06 19:13 ` dpdklab
2024-03-06 19:14 ` dpdklab
2024-03-06 19:16 ` dpdklab
2024-03-06 19:22 ` dpdklab
2024-03-06 19:23 ` dpdklab
2024-03-06 19:28 ` dpdklab
2024-03-06 19:35 ` dpdklab
2024-03-06 19:45 ` dpdklab
2024-03-06 20:03 ` dpdklab
2024-03-06 20:13 ` dpdklab
2024-03-06 20:15 ` dpdklab
2024-03-06 20:22 ` dpdklab
2024-03-06 20:25 ` dpdklab
2024-03-06 20:29 ` dpdklab
2024-03-06 20:33 ` dpdklab
2024-03-06 20:36 ` dpdklab
2024-03-06 20:45 ` dpdklab
2024-03-06 20:53 ` dpdklab
2024-03-06 21:10 ` dpdklab
2024-03-06 21:16 ` dpdklab
2024-03-06 21:17 ` dpdklab
2024-03-06 22:50 ` dpdklab
2024-03-07  0:38 ` 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=65e8bf4e.170a0220.577a2.5b68SMTPIN_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).