From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137358 [PATCH] net/mlx5: fix the HWS registers initializ
Date: Tue, 27 Feb 2024 11:58:30 -0800 (PST) [thread overview]
Message-ID: <65de3ee6.050a0220.89b07.01b5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227152627.25749-1-bingz@nvidia.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137358
_Functional Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Tuesday, February 27 2024 15:26:27
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fdcd099fbaa513409ea4185b2362d9d6623cf26e
137358 --> 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/29293/
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-27 19:58 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227152627.25749-1-bingz@nvidia.com>
2024-02-27 15:04 ` |SUCCESS| pw137358 [PATCH] net/mlx5: fix the HWS registers initialization qemudev
2024-02-27 15:08 ` qemudev
2024-02-27 15:28 ` checkpatch
2024-02-27 16:25 ` 0-day Robot
2024-02-27 19:43 ` |SUCCESS| pw137358 [PATCH] net/mlx5: fix the HWS registers initializ dpdklab
2024-02-27 19:46 ` dpdklab
2024-02-27 19:58 ` dpdklab [this message]
2024-02-27 20:06 ` dpdklab
2024-02-27 20:15 ` dpdklab
2024-02-27 20:15 ` dpdklab
2024-02-27 20:16 ` dpdklab
2024-02-27 20:23 ` dpdklab
2024-02-27 20:23 ` dpdklab
2024-02-27 20:38 ` dpdklab
2024-02-27 20:39 ` dpdklab
2024-02-27 20:42 ` dpdklab
2024-02-27 20:42 ` dpdklab
2024-02-27 20:43 ` dpdklab
2024-02-27 21:00 ` dpdklab
2024-02-27 21:00 ` dpdklab
2024-02-27 23:21 ` dpdklab
2024-02-27 23:23 ` dpdklab
2024-02-27 23:24 ` dpdklab
2024-02-27 23:26 ` dpdklab
2024-02-27 23:27 ` dpdklab
2024-02-27 23:27 ` dpdklab
2024-02-27 23:27 ` dpdklab
2024-02-27 23:27 ` dpdklab
2024-02-27 23:27 ` dpdklab
2024-02-27 23:28 ` dpdklab
2024-02-27 23:28 ` dpdklab
2024-02-27 23:28 ` dpdklab
2024-02-27 23:28 ` dpdklab
2024-02-27 23:28 ` dpdklab
2024-02-27 23:29 ` dpdklab
2024-02-27 23:29 ` dpdklab
2024-02-27 23:29 ` dpdklab
2024-02-27 23:30 ` dpdklab
2024-02-27 23:30 ` dpdklab
2024-02-27 23:31 ` dpdklab
2024-02-27 23:32 ` dpdklab
2024-02-27 23:34 ` dpdklab
2024-02-27 23:42 ` dpdklab
2024-02-27 23:43 ` dpdklab
2024-02-27 23:43 ` dpdklab
2024-02-27 23:43 ` dpdklab
2024-02-27 23:44 ` dpdklab
2024-02-27 23:44 ` dpdklab
2024-02-27 23:44 ` dpdklab
2024-02-27 23:44 ` dpdklab
2024-02-27 23:45 ` dpdklab
2024-02-27 23:45 ` dpdklab
2024-02-27 23:49 ` dpdklab
2024-02-27 23:49 ` dpdklab
2024-02-27 23:50 ` dpdklab
2024-02-27 23:50 ` dpdklab
2024-02-27 23:56 ` dpdklab
2024-02-28 0:07 ` dpdklab
2024-02-28 0:10 ` dpdklab
2024-02-28 0:32 ` dpdklab
2024-02-28 0:33 ` dpdklab
2024-02-28 0:40 ` dpdklab
2024-02-28 0:46 ` dpdklab
2024-02-28 1:00 ` dpdklab
2024-02-28 2:44 ` dpdklab
2024-02-28 2:45 ` dpdklab
2024-02-28 8:02 ` dpdklab
2024-02-28 10:38 ` dpdklab
2024-02-28 10:53 ` dpdklab
2024-02-28 17:13 ` dpdklab
2024-02-29 6:30 ` dpdklab
2024-02-29 14:13 ` dpdklab
2024-02-29 14:20 ` dpdklab
2024-02-29 14:21 ` dpdklab
2024-02-29 14:45 ` 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=65de3ee6.050a0220.89b07.01b5SMTPIN_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).