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| pw138307 [PATCH] [v3,1/1] net/mana: add vlan tagging suppo
Date: Wed, 13 Mar 2024 05:37:39 -0700 (PDT)	[thread overview]
Message-ID: <65f19e13.170a0220.6c5d4.f39bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240313090341.373037-1-weh@linux.microsoft.com>

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

_Testing PASS_

Submitter: Wei Hu <weh@linux.microsoft.com>
Date: Wednesday, March 13 2024 09:03:40 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:544d6d79a6ff0964a79a57efb102e87fdbd107d9

138307 --> testing pass

Test environment and result as below:

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


CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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

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

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

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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

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

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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

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-13 12:38 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240313090341.373037-1-weh@linux.microsoft.com>
2024-03-13  9:44 ` |SUCCESS| pw138307 [PATCH v3 1/1] net/mana: add vlan tagging support qemudev
2024-03-13  9:48 ` qemudev
2024-03-13 10:07 ` |WARNING| " checkpatch
2024-03-13 11:24 ` |SUCCESS| " 0-day Robot
2024-03-13 12:03 ` |SUCCESS| pw138307 [PATCH] [v3,1/1] net/mana: add vlan tagging suppo dpdklab
2024-03-13 12:05 ` dpdklab
2024-03-13 12:20 ` |FAILURE| " dpdklab
2024-03-13 12:20 ` |SUCCESS| " dpdklab
2024-03-13 12:21 ` dpdklab
2024-03-13 12:21 ` dpdklab
2024-03-13 12:22 ` dpdklab
2024-03-13 12:22 ` dpdklab
2024-03-13 12:23 ` dpdklab
2024-03-13 12:23 ` dpdklab
2024-03-13 12:23 ` dpdklab
2024-03-13 12:24 ` dpdklab
2024-03-13 12:25 ` dpdklab
2024-03-13 12:25 ` dpdklab
2024-03-13 12:25 ` dpdklab
2024-03-13 12:25 ` dpdklab
2024-03-13 12:26 ` dpdklab
2024-03-13 12:26 ` dpdklab
2024-03-13 12:27 ` dpdklab
2024-03-13 12:27 ` dpdklab
2024-03-13 12:28 ` dpdklab
2024-03-13 12:28 ` dpdklab
2024-03-13 12:28 ` dpdklab
2024-03-13 12:28 ` dpdklab
2024-03-13 12:28 ` dpdklab
2024-03-13 12:29 ` dpdklab
2024-03-13 12:29 ` dpdklab
2024-03-13 12:29 ` dpdklab
2024-03-13 12:30 ` dpdklab
2024-03-13 12:30 ` dpdklab
2024-03-13 12:31 ` dpdklab
2024-03-13 12:31 ` dpdklab
2024-03-13 12:31 ` dpdklab
2024-03-13 12:31 ` dpdklab
2024-03-13 12:32 ` dpdklab
2024-03-13 12:32 ` dpdklab
2024-03-13 12:32 ` dpdklab
2024-03-13 12:32 ` dpdklab
2024-03-13 12:33 ` dpdklab
2024-03-13 12:33 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:34 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:35 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:36 ` dpdklab
2024-03-13 12:37 ` dpdklab
2024-03-13 12:37 ` dpdklab [this message]
2024-03-13 12:41 ` dpdklab
2024-03-13 12:50 ` dpdklab
2024-03-13 12:50 ` dpdklab
2024-03-13 12:58 ` dpdklab
2024-03-13 13:48 ` dpdklab
2024-03-13 19:05 ` dpdklab
2024-03-13 19:06 ` dpdklab
2024-03-13 19:09 ` dpdklab
2024-03-13 19:11 ` dpdklab
2024-03-13 19:12 ` dpdklab
2024-03-13 19:13 ` dpdklab
2024-03-13 19:14 ` dpdklab
2024-03-13 19:16 ` dpdklab
2024-03-13 19:17 ` dpdklab
2024-03-13 19:24 ` dpdklab
2024-03-13 19:24 ` dpdklab
2024-03-13 19:29 ` dpdklab
2024-03-17  2:44 ` dpdklab
2024-03-17  3:20 ` dpdklab
2024-03-17  9:40 ` dpdklab
2024-03-17 10:20 ` 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=65f19e13.170a0220.6c5d4.f39bSMTPIN_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).