From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137355 [PATCH] [v2] net/mlx5: fix VLAN handling in meter
Date: Tue, 27 Feb 2024 10:21:29 -0800 (PST) [thread overview]
Message-ID: <65de2829.050a0220.55276.8737SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137355
_Functional Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Tuesday, February 27 2024 13:58:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:298ef95d4ef2a53ea39e94c2326fe2fdf6b91203
137355 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29290/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-27 18:21 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 18:21 dpdklab [this message]
[not found] <20240227135816.135279-1-dsosnowski@nvidia.com>
2024-02-27 22:10 ` dpdklab
2024-02-27 22:11 ` dpdklab
2024-02-27 22:12 ` dpdklab
2024-02-27 22:12 ` dpdklab
2024-02-27 22:13 ` dpdklab
2024-02-27 22:13 ` dpdklab
2024-02-27 22:16 ` dpdklab
2024-02-27 22:18 ` dpdklab
2024-02-27 22:20 ` dpdklab
2024-02-27 22:20 ` dpdklab
2024-02-27 22:21 ` dpdklab
2024-02-27 22:21 ` dpdklab
2024-02-27 22:22 ` dpdklab
2024-02-27 22:24 ` dpdklab
2024-02-27 22:26 ` dpdklab
2024-02-27 22:30 ` dpdklab
2024-02-27 22:31 ` dpdklab
2024-02-27 22:31 ` dpdklab
2024-02-27 22:31 ` dpdklab
2024-02-27 22:32 ` dpdklab
2024-02-27 22:39 ` dpdklab
2024-02-27 22:39 ` dpdklab
2024-02-27 22:39 ` dpdklab
2024-02-27 22:40 ` dpdklab
2024-02-27 22:41 ` dpdklab
2024-02-27 22:45 ` dpdklab
2024-02-27 22:47 ` dpdklab
2024-02-27 22:47 ` dpdklab
2024-02-27 22:47 ` dpdklab
2024-02-27 22:48 ` dpdklab
2024-02-27 22:48 ` dpdklab
2024-02-27 22:48 ` dpdklab
2024-02-27 22:48 ` dpdklab
2024-02-27 22:49 ` dpdklab
2024-02-27 22:50 ` dpdklab
2024-02-27 22:51 ` dpdklab
2024-02-27 22:54 ` dpdklab
2024-02-27 22:57 ` dpdklab
2024-02-27 23:04 ` dpdklab
2024-02-27 23:04 ` dpdklab
2024-02-27 23:12 ` dpdklab
2024-02-27 23:43 ` dpdklab
2024-02-28 0:23 ` dpdklab
2024-02-28 1:30 ` dpdklab
2024-02-28 5:16 ` dpdklab
2024-02-28 9:05 ` dpdklab
2024-02-28 9:14 ` dpdklab
2024-02-28 15:28 ` dpdklab
2024-02-29 1:51 ` dpdklab
2024-02-29 13:02 ` dpdklab
2024-02-29 13:05 ` dpdklab
2024-02-29 13:12 ` dpdklab
2024-02-29 13:18 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 19:13 dpdklab
2024-02-27 19:12 dpdklab
2024-02-27 19:12 dpdklab
2024-02-27 19:02 dpdklab
2024-02-27 19:01 dpdklab
2024-02-27 19:01 dpdklab
2024-02-27 19:01 dpdklab
2024-02-27 18:52 dpdklab
2024-02-27 18:48 dpdklab
2024-02-27 18:48 dpdklab
2024-02-27 18:47 dpdklab
2024-02-27 18:46 dpdklab
2024-02-27 18:46 dpdklab
2024-02-27 18:22 dpdklab
2024-02-27 18: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=65de2829.050a0220.55276.8737SMTPIN_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).