From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw93313 [PATCH] [v1] net/i40e: fix flow director does not work
Date: Wed, 19 May 2021 00:25:15 -0400 (EDT) [thread overview]
Message-ID: <20210519042515.DB8774B0@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/93313
_Functional Testing PASS_
Submitter: Steve Yang <stevex.yang@intel.com>
Date: Wednesday, May 19 2021 03:27:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:947dff12bcf5023255433c9997710a5635522431
93313 --> functional testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/17129/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-05-19 4:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 4:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-21 3:44 dpdklab
2021-05-21 3:25 dpdklab
2021-05-19 22:05 dpdklab
2021-05-19 21:24 dpdklab
2021-05-19 21:12 dpdklab
2021-05-19 21:00 dpdklab
2021-05-19 20:19 dpdklab
2021-05-19 16:10 dpdklab
2021-05-19 15:53 dpdklab
2021-05-19 15:42 dpdklab
2021-05-19 5:41 dpdklab
2021-05-19 4:49 dpdklab
2021-05-19 4:37 dpdklab
2021-05-19 4:19 dpdklab
2021-05-19 4:02 dpdklab
2021-05-19 3:55 dpdklab
[not found] <20210519032745.707639-1-stevex.yang@intel.com>
2021-05-19 3:29 ` [dpdk-test-report] |SUCCESS| pw93313 [PATCH v1] " 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=20210519042515.DB8774B0@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--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).