From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw97567 [PATCH] [v4] net/mlx5: fix mutex unlock in txpp cleanup
Date: Mon, 30 Aug 2021 19:09:27 -0400 (EDT) [thread overview]
Message-ID: <20210830230927.6BE611D4@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/97567
_Functional Testing PASS_
Submitter: Chengfeng Ye <cyeaa@connect.ust.hk>
Date: Monday, August 30 2021 13:31:18
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:bfd3c352eb9729f97da6e1b5e958e121542d8a8d
97567 --> 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 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 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/18426/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-08-30 23:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 23:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-01 4:02 dpdklab
2021-08-31 18:31 dpdklab
2021-08-31 12:34 dpdklab
2021-08-31 12:06 dpdklab
2021-08-31 11:38 dpdklab
2021-08-31 11:20 dpdklab
2021-08-31 2:41 dpdklab
2021-08-31 0:04 dpdklab
2021-08-30 23:47 dpdklab
2021-08-30 23:41 dpdklab
2021-08-30 23:29 dpdklab
2021-08-30 23:24 dpdklab
2021-08-30 23:04 dpdklab
2021-08-30 22:54 dpdklab
2021-08-30 22:36 dpdklab
2021-08-30 22:22 dpdklab
2021-08-30 22:07 dpdklab
2021-08-30 21:53 dpdklab
2021-08-30 21:13 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=20210830230927.6BE611D4@noxus.dpdklab.iol.unh.edu \
--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).