From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw84787 [PATCH] [v2] net/mlx5: fix flow descriptor allocation in Direct Verbs mode.
Date: Tue, 8 Dec 2020 04:22:23 -0500 (EST) [thread overview]
Message-ID: <20201208092223.A4F2588E61@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/84787
_Functional Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, December 08 2020 08:17:05
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ecc69f98c7e3dd5ecab94047edb65ccff0dce5b9
84787 --> 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 XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/14749/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-12-08 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 9:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-08 9:31 dpdklab
2020-12-08 9:13 dpdklab
2020-12-08 9:02 dpdklab
2020-12-08 8:53 dpdklab
[not found] <20201208081705.11751-1-getelson@nvidia.com>
2020-12-08 8:18 ` [dpdk-test-report] |SUCCESS| pw84787 [PATCH v2] " 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=20201208092223.A4F2588E61@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).