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| pw139626 [PATCH] [v3] net/vmxnet3: fix a missing vmxnet3 r
Date: Mon, 22 Apr 2024 12:46:53 -0700 (PDT)	[thread overview]
Message-ID: <6626bead.4a0a0220.5d8c3.50bfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240422181050.9661-1-ronak.doshi@broadcom.com>

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

_Testing PASS_

Submitter: Ronak Doshi <ronak.doshi@broadcom.com>
Date: Monday, April 22 2024 18:10:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8841786ab4aa72d205f97528af8708a13a851f4f

139626 --> testing pass

Test environment and result as below:

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


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

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

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

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

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

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-04-22 19:46 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240422181050.9661-1-ronak.doshi@broadcom.com>
2024-04-22 17:45 ` |SUCCESS| pw139626 [PATCH v3] net/vmxnet3: fix a missing vmxnet3 register command qemudev
2024-04-22 17:49 ` qemudev
2024-04-22 18:12 ` |WARNING| " checkpatch
2024-04-22 19:00 ` |SUCCESS| pw139626 [PATCH] [v3] net/vmxnet3: fix a missing vmxnet3 r dpdklab
2024-04-22 19:01 ` dpdklab
2024-04-22 19:04 ` |SUCCESS| pw139626 [PATCH v3] net/vmxnet3: fix a missing vmxnet3 register command 0-day Robot
2024-04-22 19:07 ` |SUCCESS| pw139626 [PATCH] [v3] net/vmxnet3: fix a missing vmxnet3 r dpdklab
2024-04-22 19:07 ` dpdklab
2024-04-22 19:08 ` dpdklab
2024-04-22 19:08 ` dpdklab
2024-04-22 19:08 ` dpdklab
2024-04-22 19:09 ` dpdklab
2024-04-22 19:09 ` dpdklab
2024-04-22 19:09 ` dpdklab
2024-04-22 19:10 ` dpdklab
2024-04-22 19:10 ` dpdklab
2024-04-22 19:10 ` dpdklab
2024-04-22 19:11 ` dpdklab
2024-04-22 19:11 ` dpdklab
2024-04-22 19:12 ` dpdklab
2024-04-22 19:13 ` dpdklab
2024-04-22 19:15 ` dpdklab
2024-04-22 19:16 ` dpdklab
2024-04-22 19:16 ` dpdklab
2024-04-22 19:16 ` dpdklab
2024-04-22 19:17 ` dpdklab
2024-04-22 19:17 ` dpdklab
2024-04-22 19:18 ` dpdklab
2024-04-22 19:18 ` dpdklab
2024-04-22 19:19 ` dpdklab
2024-04-22 19:20 ` dpdklab
2024-04-22 19:24 ` dpdklab
2024-04-22 19:25 ` dpdklab
2024-04-22 19:26 ` dpdklab
2024-04-22 19:26 ` dpdklab
2024-04-22 19:27 ` dpdklab
2024-04-22 19:28 ` dpdklab
2024-04-22 19:28 ` dpdklab
2024-04-22 19:29 ` dpdklab
2024-04-22 19:29 ` dpdklab
2024-04-22 19:32 ` dpdklab
2024-04-22 19:32 ` dpdklab
2024-04-22 19:32 ` dpdklab
2024-04-22 19:42 ` dpdklab
2024-04-22 19:42 ` dpdklab
2024-04-22 19:42 ` dpdklab
2024-04-22 19:42 ` dpdklab
2024-04-22 19:42 ` dpdklab
2024-04-22 19:44 ` dpdklab
2024-04-22 19:46 ` dpdklab [this message]
2024-04-22 19:47 ` dpdklab
2024-04-22 19:47 ` dpdklab
2024-04-22 19:47 ` dpdklab
2024-04-22 19:47 ` dpdklab
2024-04-22 19:47 ` dpdklab
2024-04-22 19:48 ` dpdklab
2024-04-22 19:50 ` dpdklab
2024-04-22 19:53 ` dpdklab
2024-04-22 19:54 ` dpdklab
2024-04-22 19:54 ` dpdklab
2024-04-22 19:54 ` dpdklab
2024-04-22 19:55 ` dpdklab
2024-04-22 19:56 ` dpdklab
2024-04-22 19:57 ` dpdklab
2024-04-22 20:00 ` dpdklab
2024-04-22 20:00 ` dpdklab
2024-04-22 20:00 ` dpdklab
2024-04-22 20:01 ` dpdklab
2024-04-22 20:01 ` dpdklab
2024-04-22 20:01 ` dpdklab
2024-04-22 20:01 ` dpdklab
2024-04-22 20:02 ` dpdklab
2024-04-22 20:04 ` dpdklab
2024-04-22 20:04 ` dpdklab
2024-04-22 20:04 ` dpdklab
2024-04-22 20:06 ` dpdklab
2024-04-22 20:07 ` dpdklab
2024-04-22 20:07 ` dpdklab
2024-04-22 20:07 ` dpdklab
2024-04-22 20:19 ` dpdklab
2024-04-22 20:36 ` dpdklab
2024-04-22 20:39 ` dpdklab
2024-04-22 20:47 ` dpdklab
2024-04-22 20:47 ` dpdklab
2024-04-22 20:48 ` dpdklab
2024-04-22 20:52 ` dpdklab
2024-04-22 20:58 ` dpdklab
2024-04-22 21:00 ` dpdklab
2024-04-22 21:03 ` dpdklab
2024-04-22 21:05 ` dpdklab
2024-04-22 21:40 ` 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=6626bead.4a0a0220.5d8c3.50bfSMTPIN_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).