From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138081 [PATCH] net/mlx5: prevent ioctl failure log from
Date: Thu, 07 Mar 2024 01:36:59 -0800 (PST) [thread overview]
Message-ID: <65e98abb.250a0220.db997.a954SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240307061345.310225-1-bingz@nvidia.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138081
_Functional Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Thursday, March 07 2024 06:13:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3472e5d3295d44b4835ffb22c39f2b7d40780f10
138081 --> 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/29451/
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-07 9:37 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240307061345.310225-1-bingz@nvidia.com>
2024-03-07 6:02 ` |SUCCESS| pw138081 [PATCH] net/mlx5: prevent ioctl failure log from flood qemudev
2024-03-07 6:06 ` qemudev
2024-03-07 6:16 ` checkpatch
2024-03-07 7:04 ` 0-day Robot
2024-03-07 8:51 ` |SUCCESS| pw138081 [PATCH] net/mlx5: prevent ioctl failure log from dpdklab
2024-03-07 9:01 ` dpdklab
2024-03-07 9:07 ` dpdklab
2024-03-07 9:22 ` dpdklab
2024-03-07 9:23 ` dpdklab
2024-03-07 9:26 ` dpdklab
2024-03-07 9:36 ` dpdklab [this message]
2024-03-07 9:37 ` dpdklab
2024-03-07 9:48 ` dpdklab
2024-03-07 10:07 ` dpdklab
2024-03-07 10:08 ` dpdklab
2024-03-07 10:09 ` dpdklab
2024-03-07 10:10 ` dpdklab
2024-03-07 10:10 ` dpdklab
2024-03-07 10:11 ` dpdklab
2024-03-07 10:11 ` dpdklab
2024-03-07 10:11 ` dpdklab
2024-03-07 10:29 ` dpdklab
2024-03-07 10:30 ` dpdklab
2024-03-07 10:31 ` dpdklab
2024-03-07 10:31 ` dpdklab
2024-03-07 10:32 ` dpdklab
2024-03-07 10:32 ` dpdklab
2024-03-07 10:33 ` dpdklab
2024-03-07 10:34 ` dpdklab
2024-03-07 10:35 ` dpdklab
2024-03-07 10:35 ` dpdklab
2024-03-07 10:36 ` dpdklab
2024-03-07 10:40 ` dpdklab
2024-03-07 10:41 ` dpdklab
2024-03-07 10:42 ` dpdklab
2024-03-07 10:42 ` dpdklab
2024-03-07 10:42 ` dpdklab
2024-03-07 10:42 ` dpdklab
2024-03-07 10:42 ` dpdklab
2024-03-07 10:42 ` dpdklab
2024-03-07 10:43 ` dpdklab
2024-03-07 10:43 ` dpdklab
2024-03-07 10:43 ` dpdklab
2024-03-07 10:43 ` dpdklab
2024-03-07 10:43 ` dpdklab
2024-03-07 10:44 ` dpdklab
2024-03-07 10:44 ` dpdklab
2024-03-07 10:44 ` dpdklab
2024-03-07 10:44 ` dpdklab
2024-03-07 10:45 ` dpdklab
2024-03-07 10:45 ` dpdklab
2024-03-07 10:45 ` dpdklab
2024-03-07 10:46 ` dpdklab
2024-03-07 10:48 ` dpdklab
2024-03-07 10:48 ` dpdklab
2024-03-07 10:49 ` dpdklab
2024-03-07 10:49 ` dpdklab
2024-03-07 10:49 ` dpdklab
2024-03-07 10:49 ` dpdklab
2024-03-07 10:50 ` dpdklab
2024-03-07 10:50 ` dpdklab
2024-03-07 10:52 ` dpdklab
2024-03-07 10:52 ` dpdklab
2024-03-07 11:19 ` dpdklab
2024-03-07 11:30 ` dpdklab
2024-03-07 15:37 ` dpdklab
2024-03-08 3:45 ` dpdklab
2024-03-08 3:49 ` dpdklab
2024-03-08 3:51 ` dpdklab
2024-03-08 3:54 ` dpdklab
2024-03-11 11:25 ` dpdklab
2024-03-11 12:01 ` 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=65e98abb.250a0220.db997.a954SMTPIN_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).