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| pw140382 [PATCH] net/cnxk: fix promiscuous state after MAC
Date: Tue, 28 May 2024 08:12:29 -0700 (PDT)	[thread overview]
Message-ID: <6655f45d.050a0220.cbdbf.af06SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240528083246.4016677-1-rbhansali@marvell.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140382

_Testing PASS_

Submitter: Rahul Bhansali <rbhansali@marvell.com>
Date: Tuesday, May 28 2024 08:32:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0271d6dc6c793cbe30054b5328c232a6d43d7297

140382 --> testing pass

Test environment and result as below:

+-----------------------------+--------------+----------------+---------------------------+
|         Environment         | lpm_autotest | dpdk_unit_test | cryptodev_sw_zuc_autotest |
+=============================+==============+================+===========================+
| Ubuntu 20.04 ARM SVE        | PASS         | SKIPPED        | SKIPPED                   |
+-----------------------------+--------------+----------------+---------------------------+
| 32-bit Ubuntu 20.04.4 (ARM) | SKIPPED      | PASS           | SKIPPED                   |
+-----------------------------+--------------+----------------+---------------------------+
| CentOS Stream 9 (ARM)       | SKIPPED      | PASS           | SKIPPED                   |
+-----------------------------+--------------+----------------+---------------------------+
| Debian 11 (Buster) (ARM)    | SKIPPED      | PASS           | SKIPPED                   |
+-----------------------------+--------------+----------------+---------------------------+
| Fedora 39 (ARM)             | SKIPPED      | PASS           | SKIPPED                   |
+-----------------------------+--------------+----------------+---------------------------+
| Fedora 37 (ARM)             | SKIPPED      | PASS           | SKIPPED                   |
+-----------------------------+--------------+----------------+---------------------------+
| Debian 12 (arm)             | SKIPPED      | PASS           | PASS                      |
+-----------------------------+--------------+----------------+---------------------------+


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

32-bit Ubuntu 20.04.4 (ARM)
	Kernel: 5.4.0-155-generic aarch64
	Compiler: gcc 9.4

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.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/30033/

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-28 15:12 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240528083246.4016677-1-rbhansali@marvell.com>
2024-05-28  8:09 ` |SUCCESS| pw140382 [PATCH] net/cnxk: fix promiscuous state after MAC change qemudev
2024-05-28  8:14 ` qemudev
2024-05-28  8:34 ` checkpatch
2024-05-28  9:23 ` 0-day Robot
2024-05-28 12:15 ` |SUCCESS| pw140382 [PATCH] net/cnxk: fix promiscuous state after MAC dpdklab
2024-05-28 12:28 ` dpdklab
2024-05-28 12:34 ` dpdklab
2024-05-28 12:35 ` dpdklab
2024-05-28 12:48 ` dpdklab
2024-05-28 12:52 ` dpdklab
2024-05-28 12:58 ` dpdklab
2024-05-28 13:21 ` dpdklab
2024-05-28 13:22 ` dpdklab
2024-05-28 13:22 ` dpdklab
2024-05-28 13:23 ` dpdklab
2024-05-28 13:23 ` dpdklab
2024-05-28 13:23 ` dpdklab
2024-05-28 13:23 ` dpdklab
2024-05-28 13:23 ` dpdklab
2024-05-28 13:24 ` dpdklab
2024-05-28 13:24 ` dpdklab
2024-05-28 13:25 ` dpdklab
2024-05-28 14:11 ` dpdklab
2024-05-28 14:15 ` dpdklab
2024-05-28 14:37 ` dpdklab
2024-05-28 14:37 ` dpdklab
2024-05-28 14:37 ` dpdklab
2024-05-28 14:38 ` dpdklab
2024-05-28 14:38 ` dpdklab
2024-05-28 14:39 ` dpdklab
2024-05-28 14:39 ` dpdklab
2024-05-28 14:39 ` dpdklab
2024-05-28 14:40 ` dpdklab
2024-05-28 14:40 ` dpdklab
2024-05-28 14:40 ` dpdklab
2024-05-28 14:41 ` dpdklab
2024-05-28 14:41 ` dpdklab
2024-05-28 14:41 ` dpdklab
2024-05-28 14:41 ` dpdklab
2024-05-28 14:42 ` dpdklab
2024-05-28 14:42 ` dpdklab
2024-05-28 14:43 ` dpdklab
2024-05-28 14:43 ` dpdklab
2024-05-28 14:43 ` dpdklab
2024-05-28 14:43 ` dpdklab
2024-05-28 14:43 ` dpdklab
2024-05-28 14:44 ` dpdklab
2024-05-28 14:44 ` dpdklab
2024-05-28 14:44 ` dpdklab
2024-05-28 14:44 ` dpdklab
2024-05-28 14:45 ` dpdklab
2024-05-28 14:45 ` dpdklab
2024-05-28 14:45 ` dpdklab
2024-05-28 14:45 ` dpdklab
2024-05-28 14:46 ` dpdklab
2024-05-28 14:46 ` dpdklab
2024-05-28 14:46 ` dpdklab
2024-05-28 14:47 ` dpdklab
2024-05-28 14:47 ` dpdklab
2024-05-28 14:47 ` dpdklab
2024-05-28 14:47 ` dpdklab
2024-05-28 14:48 ` dpdklab
2024-05-28 14:48 ` dpdklab
2024-05-28 14:48 ` dpdklab
2024-05-28 14:48 ` dpdklab
2024-05-28 14:48 ` dpdklab
2024-05-28 14:48 ` dpdklab
2024-05-28 14:48 ` dpdklab
2024-05-28 14:48 ` dpdklab
2024-05-28 14:49 ` dpdklab
2024-05-28 14:50 ` dpdklab
2024-05-28 14:56 ` dpdklab
2024-05-28 14:59 ` dpdklab
2024-05-28 15:01 ` dpdklab
2024-05-28 15:09 ` dpdklab
2024-05-28 15:12 ` dpdklab [this message]
2024-05-28 15:12 ` dpdklab
2024-05-28 15:16 ` dpdklab
2024-05-28 15:24 ` dpdklab
2024-05-28 15:31 ` dpdklab
2024-05-28 15:31 ` dpdklab
2024-05-28 15:37 ` dpdklab
2024-05-28 15:41 ` dpdklab
2024-05-28 15:42 ` dpdklab
2024-05-28 15:46 ` dpdklab
2024-05-28 15:56 ` dpdklab
2024-05-28 16:01 ` dpdklab
2024-05-28 16:03 ` dpdklab
2024-05-28 16:05 ` dpdklab
2024-05-30  3:15 ` dpdklab
2024-05-30  3:15 ` dpdklab
2024-05-30  3: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=6655f45d.050a0220.cbdbf.af06SMTPIN_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).