From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw87025 [PATCH] [v3] net/bnxt: fix lock handling in stop and close
Date: Thu, 21 Jan 2021 03:43:54 -0500 (EST) [thread overview]
Message-ID: <20210121084354.EA3454DC@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/87025
_Functional Testing PASS_
Submitter: Ajit Khaparde <ajitkhaparde@gmail.com>
Date: Thursday, January 21 2021 07:16:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4080917cbcb8fb41bf6b3618039a72cee0b7525e
87025 --> functional testing pass
Test environment and result as below:
Ubuntu 18.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/5
Ubuntu 18.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/15316/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-01-21 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 8:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-22 16:51 dpdklab
2021-01-22 16:18 dpdklab
2021-01-21 9:24 dpdklab
2021-01-21 9:09 dpdklab
2021-01-21 8:58 dpdklab
2021-01-21 8:44 dpdklab
2021-01-21 8:38 dpdklab
2021-01-21 8:29 dpdklab
2021-01-21 8:23 dpdklab
[not found] <20210121071656.32879-1-ajit.khaparde@broadcom.com>
2021-01-21 7:17 ` [dpdk-test-report] |SUCCESS| pw87025 [PATCH v3] " checkpatch
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=20210121084354.EA3454DC@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).