From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137464 [PATCH] net/mlx5: fix action template expansion:
Date: Thu, 29 Feb 2024 04:35:57 -0800 (PST) [thread overview]
Message-ID: <65e07a2d.170a0220.6a364.1c71SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229101955.586947-1-getelson@nvidia.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137464
_Functional Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thursday, February 29 2024 10:19:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:45d2195f9ea6ead7242af856c799c6f084d874bc
137464 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29328/
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 12:36 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229101955.586947-1-getelson@nvidia.com>
2024-02-29 9:57 ` |SUCCESS| pw137464 [PATCH] net/mlx5: fix action template expansion: support indirect actions list qemudev
2024-02-29 10:02 ` qemudev
2024-02-29 10:22 ` checkpatch
2024-02-29 11:25 ` 0-day Robot
2024-02-29 12:32 ` |SUCCESS| pw137464 [PATCH] net/mlx5: fix action template expansion: dpdklab
2024-02-29 12:35 ` dpdklab
2024-02-29 12:35 ` dpdklab [this message]
2024-02-29 12:36 ` dpdklab
2024-02-29 12:36 ` dpdklab
2024-02-29 12:38 ` dpdklab
2024-02-29 12:40 ` dpdklab
2024-02-29 12:40 ` dpdklab
2024-02-29 12:56 ` dpdklab
2024-02-29 12:58 ` dpdklab
2024-02-29 12:59 ` dpdklab
2024-02-29 13:00 ` dpdklab
2024-02-29 13:01 ` dpdklab
2024-02-29 13:02 ` dpdklab
2024-02-29 13:03 ` dpdklab
2024-02-29 13:04 ` dpdklab
2024-02-29 13:04 ` dpdklab
2024-02-29 13:06 ` dpdklab
2024-02-29 13:11 ` dpdklab
2024-02-29 13:12 ` dpdklab
2024-02-29 13:12 ` dpdklab
2024-02-29 13:12 ` dpdklab
2024-02-29 13:16 ` dpdklab
2024-02-29 13:16 ` dpdklab
2024-02-29 13:16 ` dpdklab
2024-02-29 13:17 ` dpdklab
2024-02-29 13:17 ` dpdklab
2024-02-29 13:17 ` dpdklab
2024-02-29 13:17 ` dpdklab
2024-02-29 13:18 ` dpdklab
2024-02-29 13:18 ` dpdklab
2024-02-29 13:18 ` dpdklab
2024-02-29 13:19 ` dpdklab
2024-02-29 13:19 ` dpdklab
2024-02-29 13:20 ` dpdklab
2024-02-29 13:22 ` dpdklab
2024-02-29 13:32 ` dpdklab
2024-02-29 13:33 ` dpdklab
2024-02-29 13:33 ` dpdklab
2024-02-29 13:34 ` dpdklab
2024-02-29 13:34 ` dpdklab
2024-02-29 13:35 ` dpdklab
2024-02-29 13:40 ` dpdklab
2024-02-29 13:40 ` dpdklab
2024-02-29 13:41 ` dpdklab
2024-02-29 13:44 ` dpdklab
2024-02-29 13:44 ` dpdklab
2024-02-29 13:45 ` dpdklab
2024-02-29 13:45 ` dpdklab
2024-02-29 13:45 ` dpdklab
2024-02-29 13:46 ` dpdklab
2024-02-29 13:46 ` dpdklab
2024-02-29 13:46 ` dpdklab
2024-02-29 13:46 ` dpdklab
2024-02-29 13:47 ` dpdklab
2024-02-29 13:48 ` dpdklab
2024-02-29 13:53 ` dpdklab
2024-02-29 13:54 ` dpdklab
2024-02-29 14:00 ` dpdklab
2024-02-29 14:08 ` dpdklab
2024-02-29 14:12 ` dpdklab
2024-02-29 16:28 ` dpdklab
2024-03-01 5:42 ` dpdklab
2024-03-01 5:42 ` dpdklab
2024-03-01 5:43 ` dpdklab
2024-03-01 5:45 ` dpdklab
2024-03-02 4:59 ` dpdklab
2024-03-02 20:43 ` dpdklab
2024-03-02 21:06 ` dpdklab
2024-03-02 21:48 ` 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=65e07a2d.170a0220.6a364.1c71SMTPIN_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).