From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130082-130084 [PATCH] [v2,3/3] test/dma: add SG copy tes
Date: Thu, 10 Aug 2023 13:11:06 -0700 (PDT) [thread overview]
Message-ID: <64d5445a.0c0a0220.d8ab2.2586SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/130084
_Functional Testing PASS_
Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Thursday, August 10 2023 12:36:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70b6941e4e22d67bc10495d1638234a7e974f582
130082-130084 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.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/4
Ubuntu 20.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/4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27278/
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 20:11 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 20:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 3:04 dpdklab
2023-08-14 2:52 dpdklab
2023-08-14 2:50 dpdklab
2023-08-14 2:50 dpdklab
2023-08-14 2:48 dpdklab
2023-08-14 2:48 dpdklab
2023-08-14 2:47 dpdklab
2023-08-14 2:46 dpdklab
2023-08-14 2:46 dpdklab
2023-08-13 23:20 dpdklab
2023-08-13 19:24 dpdklab
2023-08-11 9:31 dpdklab
2023-08-11 9:24 dpdklab
2023-08-11 9:04 dpdklab
2023-08-11 9:00 dpdklab
2023-08-11 8:48 dpdklab
2023-08-11 5:40 dpdklab
2023-08-11 0:39 dpdklab
2023-08-10 22:16 dpdklab
2023-08-10 22:15 dpdklab
2023-08-10 21:48 dpdklab
2023-08-10 21:47 dpdklab
2023-08-10 21:45 dpdklab
2023-08-10 21:45 dpdklab
2023-08-10 21:43 dpdklab
2023-08-10 21:42 dpdklab
2023-08-10 21:41 dpdklab
2023-08-10 21:40 dpdklab
2023-08-10 21:33 dpdklab
2023-08-10 21:32 dpdklab
2023-08-10 21:32 dpdklab
2023-08-10 21:30 dpdklab
2023-08-10 21:29 dpdklab
2023-08-10 21:17 dpdklab
2023-08-10 21:06 dpdklab
2023-08-10 20:48 dpdklab
2023-08-10 20:42 dpdklab
2023-08-10 20:41 dpdklab
2023-08-10 20:41 dpdklab
2023-08-10 20:41 dpdklab
2023-08-10 20:40 dpdklab
2023-08-10 20:40 dpdklab
2023-08-10 20:40 dpdklab
2023-08-10 20:39 dpdklab
2023-08-10 20:39 dpdklab
2023-08-10 20:39 dpdklab
2023-08-10 20:37 dpdklab
2023-08-10 20:37 dpdklab
2023-08-10 20:37 dpdklab
2023-08-10 20:36 dpdklab
2023-08-10 20:35 dpdklab
2023-08-10 20:35 dpdklab
2023-08-10 20:34 dpdklab
2023-08-10 20:32 dpdklab
2023-08-10 20:32 dpdklab
2023-08-10 20:31 dpdklab
2023-08-10 20:31 dpdklab
2023-08-10 20:08 dpdklab
2023-08-10 19:41 dpdklab
2023-08-10 19:17 dpdklab
2023-08-10 17:38 dpdklab
2023-08-10 17:37 dpdklab
2023-08-10 17:36 dpdklab
2023-08-10 17:32 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=64d5445a.0c0a0220.d8ab2.2586SMTPIN_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).