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| pw139758 [PATCH] cmdline: configure input buffer size
Date: Tue, 30 Apr 2024 23:30:17 -0700 (PDT)	[thread overview]
Message-ID: <6631e179.920a0220.c3eb6.07ceSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240501052659.231457-1-getelson@nvidia.com>

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139758

_Testing PASS_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Wednesday, May 01 2024 05:26:59 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139758 --> testing pass

Test environment and result as below:

+----------------------+--------------------+
|     Environment      | dpdk_meson_compile |
+======================+====================+
| Ubuntu 20.04 ARM SVE | PASS               |
+----------------------+--------------------+
| Debian 12 with MUSDK | PASS               |
+----------------------+--------------------+
| Fedora 37 (ARM)      | PASS               |
+----------------------+--------------------+
| Fedora 38 (ARM)      | PASS               |
+----------------------+--------------------+
| Debian 12 (arm)      | PASS               |
+----------------------+--------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

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

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-01  6:30 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240501052659.231457-1-getelson@nvidia.com>
2024-05-01  5:08 ` qemudev
2024-05-01  5:13 ` qemudev
2024-05-01  6:23 ` 0-day Robot
2024-05-01  6:29 ` dpdklab
2024-05-01  6:30 ` dpdklab
2024-05-01  6:30 ` dpdklab [this message]
2024-05-01  6:31 ` dpdklab
2024-05-01  6:31 ` dpdklab
2024-05-01  6:31 ` |FAILURE| " dpdklab
2024-05-01  6:31 ` |SUCCESS| " dpdklab
2024-05-01  6:32 ` |FAILURE| " dpdklab
2024-05-01  6:32 ` |SUCCESS| " dpdklab
2024-05-01  6:32 ` dpdklab
2024-05-01  6:32 ` |FAILURE| " dpdklab
2024-05-01  6:33 ` |SUCCESS| " dpdklab
2024-05-01  6:33 ` dpdklab
2024-05-01  6:34 ` dpdklab
2024-05-01  6:34 ` dpdklab
2024-05-01  6:35 ` dpdklab
2024-05-01  6:35 ` dpdklab
2024-05-01  6:35 ` dpdklab
2024-05-01  6:35 ` dpdklab
2024-05-01  6:36 ` dpdklab
2024-05-01  6:36 ` dpdklab
2024-05-01  6:36 ` dpdklab
2024-05-01  6:36 ` dpdklab
2024-05-01  6:36 ` dpdklab
2024-05-01  6:37 ` dpdklab
2024-05-01  6:37 ` dpdklab
2024-05-01  6:37 ` dpdklab
2024-05-01  6:37 ` dpdklab
2024-05-01  6:37 ` dpdklab
2024-05-01  6:38 ` dpdklab
2024-05-01  6:38 ` dpdklab
2024-05-01  6:39 ` dpdklab
2024-05-01  6:39 ` dpdklab
2024-05-01  6:39 ` dpdklab
2024-05-01  6:40 ` dpdklab
2024-05-01  6:40 ` dpdklab
2024-05-01  6:40 ` dpdklab
2024-05-01  6:40 ` dpdklab
2024-05-01  6:40 ` dpdklab
2024-05-01  6:42 ` dpdklab
2024-05-01  6:42 ` dpdklab
2024-05-01  6:43 ` dpdklab
2024-05-01  6:43 ` dpdklab
2024-05-01  6:43 ` dpdklab
2024-05-01  6:45 ` dpdklab
2024-05-01  6:46 ` dpdklab
2024-05-01  6:47 ` dpdklab
2024-05-01  6:48 ` dpdklab
2024-05-01  6:49 ` dpdklab
2024-05-01  6:49 ` dpdklab
2024-05-01  6:51 ` dpdklab
2024-05-01  6:51 ` dpdklab
2024-05-01  6:53 ` dpdklab
2024-05-01  6:54 ` dpdklab
2024-05-01  6:54 ` dpdklab
2024-05-01  6:56 ` dpdklab
2024-05-01  6:58 ` dpdklab
2024-05-01  6:58 ` dpdklab
2024-05-01  6:59 ` dpdklab
2024-05-01  7:00 ` dpdklab
2024-05-01  7:00 ` dpdklab
2024-05-01  7:00 ` dpdklab
2024-05-01  7:01 ` dpdklab
2024-05-01  7:03 ` dpdklab
2024-05-01  7:05 ` dpdklab
2024-05-01  7:06 ` dpdklab
2024-05-01  7:07 ` dpdklab
2024-05-01  7:09 ` dpdklab
2024-05-01  7:11 ` dpdklab
2024-05-01  7:11 ` dpdklab
2024-05-01  7:12 ` dpdklab
2024-05-01  7:17 ` dpdklab
2024-05-01  7:18 ` dpdklab
2024-05-01  7:23 ` dpdklab
2024-05-01  7:23 ` dpdklab
2024-05-01  7:23 ` dpdklab
2024-05-01  7:25 ` dpdklab
2024-05-01  7:43 ` dpdklab
2024-05-01  7:44 ` dpdklab
2024-05-01  9:02 ` dpdklab
2024-05-01  9:34 ` dpdklab
2024-05-04  0:29 ` dpdklab
2024-05-04 11:10 ` dpdklab
2024-05-04 11:15 ` |FAILURE| " dpdklab
2024-05-04 11:19 ` |SUCCESS| " dpdklab
2024-05-04 11:22 ` dpdklab
2024-05-04 11:42 ` |FAILURE| " 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=6631e179.920a0220.c3eb6.07ceSMTPIN_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).