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| pw139826 [PATCH] [v3] cmdline: increase input buffer size
Date: Fri, 03 May 2024 00:50:51 -0700 (PDT)	[thread overview]
Message-ID: <6634975b.050a0220.25f6c.8796SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240503042715.344550-1-getelson@nvidia.com>

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

_Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Friday, May 03 2024 04:27:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139826 --> testing pass

Test environment and result as below:

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


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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

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

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)

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/29905/

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-03  7:50 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240503042715.344550-1-getelson@nvidia.com>
2024-05-03  4:09 ` |SUCCESS| pw139826 [PATCH v3] " qemudev
2024-05-03  4:13 ` qemudev
2024-05-03  5:23 ` 0-day Robot
2024-05-03  5:40 ` |SUCCESS| pw139826 [PATCH] [v3] " dpdklab
2024-05-03  5:55 ` dpdklab
2024-05-03  6:03 ` dpdklab
2024-05-03  6:03 ` dpdklab
2024-05-03  6:04 ` dpdklab
2024-05-03  6:04 ` dpdklab
2024-05-03  6:10 ` dpdklab
2024-05-03  6:12 ` dpdklab
2024-05-03  6:18 ` dpdklab
2024-05-03  6:19 ` dpdklab
2024-05-03  6:19 ` dpdklab
2024-05-03  6:19 ` dpdklab
2024-05-03  6:19 ` dpdklab
2024-05-03  6:20 ` dpdklab
2024-05-03  6:20 ` dpdklab
2024-05-03  6:20 ` dpdklab
2024-05-03  6:21 ` dpdklab
2024-05-03  6:22 ` dpdklab
2024-05-03  6:22 ` dpdklab
2024-05-03  6:23 ` dpdklab
2024-05-03  6:24 ` dpdklab
2024-05-03  6:24 ` dpdklab
2024-05-03  6:31 ` dpdklab
2024-05-03  6:32 ` dpdklab
2024-05-03  6:33 ` dpdklab
2024-05-03  6:33 ` dpdklab
2024-05-03  6:33 ` dpdklab
2024-05-03  6:41 ` dpdklab
2024-05-03  6:43 ` dpdklab
2024-05-03  6:43 ` dpdklab
2024-05-03  6:43 ` dpdklab
2024-05-03  6:46 ` dpdklab
2024-05-03  6:47 ` dpdklab
2024-05-03  6:48 ` dpdklab
2024-05-03  6:48 ` dpdklab
2024-05-03  6:49 ` dpdklab
2024-05-03  6:50 ` dpdklab
2024-05-03  6:52 ` dpdklab
2024-05-03  6:53 ` dpdklab
2024-05-03  6:55 ` dpdklab
2024-05-03  6:55 ` dpdklab
2024-05-03  6:55 ` dpdklab
2024-05-03  6:59 ` dpdklab
2024-05-03  6:59 ` dpdklab
2024-05-03  7:00 ` dpdklab
2024-05-03  7:00 ` dpdklab
2024-05-03  7:01 ` dpdklab
2024-05-03  7:01 ` dpdklab
2024-05-03  7:02 ` dpdklab
2024-05-03  7:03 ` dpdklab
2024-05-03  7:03 ` dpdklab
2024-05-03  7:15 ` dpdklab
2024-05-03  7:15 ` dpdklab
2024-05-03  7:16 ` dpdklab
2024-05-03  7:17 ` dpdklab
2024-05-03  7:17 ` dpdklab
2024-05-03  7:17 ` dpdklab
2024-05-03  7:18 ` dpdklab
2024-05-03  7:18 ` dpdklab
2024-05-03  7:19 ` dpdklab
2024-05-03  7:25 ` dpdklab
2024-05-03  7:26 ` dpdklab
2024-05-03  7:45 ` dpdklab
2024-05-03  7:46 ` dpdklab
2024-05-03  7:48 ` dpdklab
2024-05-03  7:49 ` dpdklab
2024-05-03  7:50 ` dpdklab [this message]
2024-05-03  7:52 ` dpdklab
2024-05-03  7:54 ` dpdklab
2024-05-03  7:55 ` dpdklab
2024-05-03  7:56 ` dpdklab
2024-05-03  8:10 ` dpdklab
2024-05-03  8:11 ` dpdklab
2024-05-03  8:14 ` dpdklab
2024-05-03  8:19 ` |SUCCESS| pw139826 [PATCH v3] " checkpatch
2024-05-03  8:20 ` |SUCCESS| pw139826 [PATCH] [v3] " dpdklab
2024-05-03  8:34 ` dpdklab
2024-05-03  8:46 ` dpdklab
2024-05-03  8:55 ` dpdklab
2024-05-03  9:16 ` dpdklab
2024-05-03  9:33 ` dpdklab
2024-05-03  9:47 ` dpdklab
2024-05-03  9:48 ` |SUCCESS| pw139826 [PATCH v3] " checkpatch
2024-05-03  9:56 ` checkpatch
2024-05-03 17:54 ` |SUCCESS| pw139826 [PATCH] [v3] " dpdklab
2024-05-05  2:31 ` dpdklab
2024-05-05  2:35 ` dpdklab
2024-05-05  2:39 ` dpdklab
2024-05-05  2:43 ` dpdklab
2024-05-05  3:02 ` dpdklab
2024-05-06 10:23 ` 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=6634975b.050a0220.25f6c.8796SMTPIN_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).