From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138061-138063 [PATCH] [4/4] net/mlx5: fix flow configure
Date: Wed, 06 Mar 2024 14:42:21 -0800 (PST) [thread overview]
Message-ID: <65e8f14d.050a0220.4bb33.c51bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240306202150.79577-4-dsosnowski@nvidia.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138063
_Functional Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wednesday, March 06 2024 20:21:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3472e5d3295d44b4835ffb22c39f2b7d40780f10
138061-138063 --> functional testing pass
Test environment and result as below:
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
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 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29444/
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-03-06 22:42 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306202150.79577-4-dsosnowski@nvidia.com>
2024-03-06 20:01 ` |SUCCESS| pw138061-138063 [PATCH 4/4] net/mlx5: fix flow configure validation qemudev
2024-03-06 20:05 ` qemudev
2024-03-06 20:25 ` |SUCCESS| pw138063 " checkpatch
2024-03-06 21:24 ` 0-day Robot
2024-03-06 22:38 ` |SUCCESS| pw138061-138063 [PATCH] [4/4] net/mlx5: fix flow configure dpdklab
2024-03-06 22:38 ` dpdklab
2024-03-06 22:39 ` dpdklab
2024-03-06 22:39 ` dpdklab
2024-03-06 22:39 ` dpdklab
2024-03-06 22:40 ` dpdklab
2024-03-06 22:41 ` dpdklab
2024-03-06 22:41 ` dpdklab
2024-03-06 22:42 ` dpdklab
2024-03-06 22:42 ` dpdklab [this message]
2024-03-06 22:42 ` dpdklab
2024-03-06 22:43 ` dpdklab
2024-03-06 22:43 ` dpdklab
2024-03-06 22:44 ` dpdklab
2024-03-06 22:45 ` dpdklab
2024-03-06 22:45 ` dpdklab
2024-03-06 22:45 ` dpdklab
2024-03-06 22:46 ` dpdklab
2024-03-06 22:46 ` dpdklab
2024-03-06 22:46 ` dpdklab
2024-03-06 22:46 ` dpdklab
2024-03-06 22:46 ` dpdklab
2024-03-06 22:47 ` dpdklab
2024-03-06 22:47 ` dpdklab
2024-03-06 22:47 ` dpdklab
2024-03-06 22:47 ` dpdklab
2024-03-06 22:47 ` dpdklab
2024-03-06 22:48 ` dpdklab
2024-03-06 22:48 ` dpdklab
2024-03-06 22:48 ` dpdklab
2024-03-06 22:49 ` dpdklab
2024-03-06 22:51 ` dpdklab
2024-03-06 22:51 ` dpdklab
2024-03-06 22:51 ` dpdklab
2024-03-06 22:52 ` dpdklab
2024-03-06 22:52 ` dpdklab
2024-03-06 22:52 ` dpdklab
2024-03-06 22:53 ` dpdklab
2024-03-06 22:54 ` dpdklab
2024-03-06 22:55 ` dpdklab
2024-03-06 22:55 ` dpdklab
2024-03-06 22:56 ` dpdklab
2024-03-06 22:56 ` dpdklab
2024-03-06 22:56 ` dpdklab
2024-03-06 22:56 ` dpdklab
2024-03-06 22:56 ` dpdklab
2024-03-06 22:58 ` dpdklab
2024-03-06 22:58 ` dpdklab
2024-03-06 22:59 ` dpdklab
2024-03-06 23:00 ` dpdklab
2024-03-06 23:02 ` dpdklab
2024-03-06 23:02 ` dpdklab
2024-03-06 23:03 ` dpdklab
2024-03-06 23:04 ` dpdklab
2024-03-06 23:07 ` dpdklab
2024-03-06 23:07 ` dpdklab
2024-03-06 23:08 ` dpdklab
2024-03-06 23:09 ` dpdklab
2024-03-06 23:09 ` dpdklab
2024-03-06 23:13 ` dpdklab
2024-03-06 23:19 ` dpdklab
2024-03-06 23:19 ` dpdklab
2024-03-06 23:20 ` dpdklab
2024-03-06 23:37 ` dpdklab
2024-03-07 1:31 ` dpdklab
2024-03-07 3:10 ` dpdklab
2024-03-08 0:10 ` |FAILURE| " dpdklab
2024-03-08 0:15 ` |SUCCESS| " dpdklab
2024-03-08 0:20 ` dpdklab
2024-03-08 0:25 ` 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=65e8f14d.050a0220.4bb33.c51bSMTPIN_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).