From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130085-130086 [PATCH] [v3,2/2] app/dma-perf: add SG copy
Date: Thu, 10 Aug 2023 10:24:13 -0700 (PDT) [thread overview]
Message-ID: <64d51d3d.020a0220.10d02.53feSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/130086
_Functional Testing PASS_
Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Thursday, August 10 2023 13:01:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70b6941e4e22d67bc10495d1638234a7e974f582
130085-130086 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27279/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-10 17:24 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 17:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 2:54 dpdklab
2023-08-14 2:48 dpdklab
2023-08-14 2:45 dpdklab
2023-08-14 2:45 dpdklab
2023-08-14 2:45 dpdklab
2023-08-14 2:43 dpdklab
2023-08-14 2:41 dpdklab
2023-08-14 2:40 dpdklab
2023-08-14 2:39 dpdklab
2023-08-13 23:11 dpdklab
2023-08-13 19:28 dpdklab
2023-08-11 8:42 dpdklab
2023-08-11 8:37 dpdklab
2023-08-11 8:32 dpdklab
2023-08-11 8:28 dpdklab
2023-08-11 8:11 dpdklab
2023-08-11 4:04 dpdklab
2023-08-11 0:08 dpdklab
2023-08-10 21:45 dpdklab
2023-08-10 21:44 dpdklab
2023-08-10 21:28 dpdklab
2023-08-10 21:27 dpdklab
2023-08-10 21:26 dpdklab
2023-08-10 21:26 dpdklab
2023-08-10 21:26 dpdklab
2023-08-10 21:25 dpdklab
2023-08-10 21:24 dpdklab
2023-08-10 21:22 dpdklab
2023-08-10 21:21 dpdklab
2023-08-10 21:21 dpdklab
2023-08-10 21:10 dpdklab
2023-08-10 20:38 dpdklab
2023-08-10 20:32 dpdklab
2023-08-10 20:08 dpdklab
2023-08-10 19:56 dpdklab
2023-08-10 19:56 dpdklab
2023-08-10 19:55 dpdklab
2023-08-10 19:54 dpdklab
2023-08-10 19:53 dpdklab
2023-08-10 19:52 dpdklab
2023-08-10 19:44 dpdklab
2023-08-10 19:44 dpdklab
2023-08-10 19:44 dpdklab
2023-08-10 19:41 dpdklab
2023-08-10 19:41 dpdklab
2023-08-10 19:40 dpdklab
2023-08-10 19:40 dpdklab
2023-08-10 19:40 dpdklab
2023-08-10 19:40 dpdklab
2023-08-10 19:38 dpdklab
2023-08-10 19:35 dpdklab
2023-08-10 19:35 dpdklab
2023-08-10 19:33 dpdklab
2023-08-10 19:33 dpdklab
2023-08-10 19:32 dpdklab
2023-08-10 19:31 dpdklab
2023-08-10 19:31 dpdklab
2023-08-10 19:30 dpdklab
2023-08-10 19:28 dpdklab
2023-08-10 19:27 dpdklab
2023-08-10 19:12 dpdklab
2023-08-10 18:58 dpdklab
2023-08-10 17:21 dpdklab
2023-08-10 17:21 dpdklab
2023-08-10 17:21 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=64d51d3d.020a0220.10d02.53feSMTPIN_ADDED_MISSING@mx.google.com \
--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).