From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136005 [PATCH] net/mana: rename mana_find_pmd_mr() to ma
Date: Fri, 19 Jan 2024 19:04:53 -0800 (PST) [thread overview]
Message-ID: <65ab3855.170a0220.d18c3.3bc0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136005
_Functional Testing PASS_
Submitter: Long Li <longli@linuxonhyperv.com>
Date: Saturday, January 20 2024 00:55:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39a8b1251b204d3898b4c462184f60bda1b64698
136005 --> functional testing pass
Test environment and result as below:
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
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/28918/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-20 3:04 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 3:04 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-22 19:11 dpdklab
2024-01-22 19:04 dpdklab
2024-01-20 13:55 dpdklab
2024-01-20 8:21 dpdklab
2024-01-20 7:46 dpdklab
2024-01-20 4:23 dpdklab
2024-01-20 3:47 dpdklab
2024-01-20 3:46 dpdklab
2024-01-20 3:45 dpdklab
2024-01-20 3:45 dpdklab
2024-01-20 3:44 dpdklab
2024-01-20 3:43 dpdklab
2024-01-20 3:43 dpdklab
2024-01-20 3:42 dpdklab
2024-01-20 3:36 dpdklab
2024-01-20 3:35 dpdklab
2024-01-20 3:33 dpdklab
2024-01-20 3:33 dpdklab
2024-01-20 3:33 dpdklab
2024-01-20 3:32 dpdklab
2024-01-20 3:31 dpdklab
2024-01-20 3:29 dpdklab
2024-01-20 3:29 dpdklab
2024-01-20 3:26 dpdklab
2024-01-20 3:22 dpdklab
2024-01-20 3:21 dpdklab
2024-01-20 3:21 dpdklab
2024-01-20 3:20 dpdklab
2024-01-20 3:20 dpdklab
2024-01-20 3:20 dpdklab
2024-01-20 3:20 dpdklab
2024-01-20 3:20 dpdklab
2024-01-20 3:19 dpdklab
2024-01-20 3:19 dpdklab
2024-01-20 3:19 dpdklab
2024-01-20 3:19 dpdklab
2024-01-20 3:18 dpdklab
2024-01-20 3:18 dpdklab
2024-01-20 3:18 dpdklab
2024-01-20 3:18 dpdklab
2024-01-20 3:17 dpdklab
2024-01-20 3:17 dpdklab
2024-01-20 3:17 dpdklab
2024-01-20 3:16 dpdklab
2024-01-20 3:15 dpdklab
2024-01-20 3:15 dpdklab
2024-01-20 3:14 dpdklab
2024-01-20 3:14 dpdklab
2024-01-20 3:14 dpdklab
2024-01-20 3:13 dpdklab
2024-01-20 3:12 dpdklab
2024-01-20 3:11 dpdklab
2024-01-20 3:11 dpdklab
2024-01-20 3:10 dpdklab
2024-01-20 3:10 dpdklab
2024-01-20 3:09 dpdklab
2024-01-20 3:09 dpdklab
2024-01-20 3:09 dpdklab
2024-01-20 3:08 dpdklab
2024-01-20 3:07 dpdklab
2024-01-20 3:06 dpdklab
2024-01-20 3:06 dpdklab
2024-01-20 3:03 dpdklab
2024-01-20 3:03 dpdklab
2024-01-20 3:02 dpdklab
2024-01-20 2:44 dpdklab
2024-01-20 2:41 dpdklab
2024-01-20 2:32 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=65ab3855.170a0220.d18c3.3bc0SMTPIN_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).