From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137343 [PATCH] net/mlx5: fix VLAN handling in meter spli
Date: Thu, 29 Feb 2024 02:29:26 -0800 (PST) [thread overview]
Message-ID: <65e05c86.050a0220.329da.37ddSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227111848.123687-1-dsosnowski@nvidia.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137343
_Functional Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Tuesday, February 27 2024 11:18:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:04730616fb3c8c81236def5f353b307057185e3d
137343 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29285/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-02-29 10:29 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227111848.123687-1-dsosnowski@nvidia.com>
2024-02-27 11:00 ` |SUCCESS| pw137343 [PATCH] net/mlx5: fix VLAN handling in meter split qemudev
2024-02-27 11:05 ` qemudev
2024-02-27 11:20 ` checkpatch
2024-02-27 12:25 ` 0-day Robot
2024-02-27 19:45 ` |SUCCESS| pw137343 [PATCH] net/mlx5: fix VLAN handling in meter spli dpdklab
2024-02-27 19:56 ` dpdklab
2024-02-27 22:52 ` dpdklab
2024-02-27 22:59 ` dpdklab
2024-02-28 6:34 ` dpdklab
2024-02-28 6:42 ` dpdklab
2024-02-28 6:46 ` dpdklab
2024-02-28 14:36 ` dpdklab
2024-02-29 10:04 ` dpdklab
2024-02-29 10:05 ` dpdklab
2024-02-29 10:29 ` dpdklab [this message]
2024-02-29 10:30 ` dpdklab
2024-02-27 13:31 dpdklab
2024-02-27 13:36 dpdklab
2024-02-27 13:36 dpdklab
2024-02-27 13:45 dpdklab
2024-02-27 13:56 dpdklab
2024-02-27 14:20 dpdklab
2024-02-27 14:21 dpdklab
2024-02-27 14:22 dpdklab
2024-02-27 14:22 dpdklab
2024-02-27 14:29 dpdklab
2024-02-27 14:29 dpdklab
2024-02-27 14:30 dpdklab
2024-02-27 14:30 dpdklab
2024-02-27 14:31 dpdklab
2024-02-27 14:31 dpdklab
2024-02-27 14:34 dpdklab
2024-02-27 18:04 dpdklab
2024-02-27 18:06 dpdklab
2024-02-27 18:07 dpdklab
2024-02-27 18:08 dpdklab
2024-02-27 18:09 dpdklab
2024-02-27 18:09 dpdklab
2024-02-27 18:09 dpdklab
2024-02-27 18:10 dpdklab
2024-02-27 18:12 dpdklab
2024-02-27 18:12 dpdklab
2024-02-27 18:18 dpdklab
2024-02-27 18:19 dpdklab
2024-02-27 18:19 dpdklab
2024-02-27 18:19 dpdklab
2024-02-27 18:20 dpdklab
2024-02-27 18:20 dpdklab
2024-02-27 18:20 dpdklab
2024-02-27 18:21 dpdklab
2024-02-27 18:21 dpdklab
2024-02-27 18:21 dpdklab
2024-02-27 18:24 dpdklab
2024-02-27 18:24 dpdklab
2024-02-27 18:25 dpdklab
2024-02-27 18:26 dpdklab
2024-02-27 18:27 dpdklab
2024-02-27 18:27 dpdklab
2024-02-27 18:27 dpdklab
2024-02-27 18:28 dpdklab
2024-02-27 18:28 dpdklab
2024-02-27 18:29 dpdklab
2024-02-27 18:31 dpdklab
2024-02-27 18:33 dpdklab
2024-02-27 18:39 dpdklab
2024-02-27 18:40 dpdklab
2024-02-27 18:46 dpdklab
2024-02-27 18:47 dpdklab
2024-02-27 19:02 dpdklab
2024-02-27 19:13 dpdklab
2024-02-27 19:14 dpdklab
2024-02-27 19:17 dpdklab
2024-02-27 19:18 dpdklab
2024-02-27 19:26 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=65e05c86.050a0220.329da.37ddSMTPIN_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).