From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw105233 [PATCH] app/testpmd: fix external buffer allocation
Date: Fri, 17 Dec 2021 05:42:36 -0500 (EST) [thread overview]
Message-ID: <20211217104236.7C22A306AE@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/105233
_Functional Testing PASS_
Submitter: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
Date: Friday, December 17 2021 09:58:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:042f5a355a57b31a9f87824173a9d427b21abdb8
105233 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/20514/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-12-17 10:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 10:42 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-17 10:50 dpdklab
2021-12-17 10:45 dpdklab
2021-12-17 10:45 dpdklab
2021-12-17 10:43 dpdklab
2021-12-17 10:43 dpdklab
2021-12-17 10:41 dpdklab
2021-12-17 10:39 dpdklab
2021-12-17 10:36 dpdklab
2021-12-17 10:34 dpdklab
2021-12-17 10:34 dpdklab
2021-12-17 10:31 dpdklab
2021-12-17 10:28 dpdklab
[not found] <20211217095816.2599242-1-dkozlyuk@nvidia.com>
2021-12-17 10:00 ` checkpatch
2021-12-17 10:38 ` 0-day Robot
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=20211217104236.7C22A306AE@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=ajit.khaparde@broadcom.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).