From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137362-137360 [PATCH] [v9,4/4] app/dma-perf: add SG copy
Date: Wed, 28 Feb 2024 02:32:44 -0800 (PST) [thread overview]
Message-ID: <65df0bcc.d40a0220.0ddd.db96SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227160031.3931694-5-amitprakashs@marvell.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137360
_Functional Testing PASS_
Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Tuesday, February 27 2024 16:00:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137362-137360 --> 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/3
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/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29294/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-02-28 10:33 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227160031.3931694-5-amitprakashs@marvell.com>
2024-02-27 15:59 ` |SUCCESS| pw137362-137360 [PATCH v9 4/4] app/dma-perf: add SG copy support qemudev
2024-02-27 16:03 ` qemudev
2024-02-27 16:23 ` |SUCCESS| pw137360 " checkpatch
2024-02-27 17:25 ` 0-day Robot
2024-02-27 19:58 ` |SUCCESS| pw137362-137360 [PATCH] [v9,4/4] app/dma-perf: add SG copy dpdklab
2024-02-27 20:07 ` dpdklab
2024-02-27 20:08 ` dpdklab
2024-02-27 20:13 ` dpdklab
2024-02-27 20:14 ` dpdklab
2024-02-27 20:14 ` dpdklab
2024-02-27 20:24 ` dpdklab
2024-02-27 20:40 ` dpdklab
2024-02-27 20:54 ` dpdklab
2024-02-27 21:00 ` dpdklab
2024-02-27 22:54 ` dpdklab
2024-02-27 22:55 ` dpdklab
2024-02-27 22:56 ` dpdklab
2024-02-27 22:56 ` dpdklab
2024-02-27 22:57 ` dpdklab
2024-02-27 22:57 ` dpdklab
2024-02-27 22:57 ` dpdklab
2024-02-27 22:57 ` dpdklab
2024-02-27 22:57 ` dpdklab
2024-02-27 22:57 ` dpdklab
2024-02-27 22:58 ` dpdklab
2024-02-27 22:58 ` dpdklab
2024-02-27 22:59 ` dpdklab
2024-02-27 23:00 ` dpdklab
2024-02-27 23:04 ` dpdklab
2024-02-27 23:05 ` dpdklab
2024-02-27 23:05 ` dpdklab
2024-02-27 23:05 ` dpdklab
2024-02-27 23:05 ` dpdklab
2024-02-27 23:09 ` dpdklab
2024-02-27 23:11 ` dpdklab
2024-02-27 23:12 ` dpdklab
2024-02-27 23:12 ` dpdklab
2024-02-27 23:13 ` dpdklab
2024-02-27 23:13 ` dpdklab
2024-02-27 23:14 ` dpdklab
2024-02-27 23:14 ` dpdklab
2024-02-27 23:14 ` dpdklab
2024-02-27 23:14 ` dpdklab
2024-02-27 23:14 ` dpdklab
2024-02-27 23:14 ` dpdklab
2024-02-27 23:15 ` dpdklab
2024-02-27 23:22 ` dpdklab
2024-02-27 23:22 ` dpdklab
2024-02-27 23:22 ` dpdklab
2024-02-27 23:25 ` dpdklab
2024-02-27 23:26 ` dpdklab
2024-02-27 23:28 ` dpdklab
2024-02-27 23:32 ` dpdklab
2024-02-27 23:43 ` dpdklab
2024-02-27 23:50 ` dpdklab
2024-02-27 23:59 ` dpdklab
2024-02-28 0:27 ` dpdklab
2024-02-28 0:41 ` dpdklab
2024-02-28 2:09 ` dpdklab
2024-02-28 7:12 ` dpdklab
2024-02-28 10:30 ` dpdklab
2024-02-28 10:32 ` dpdklab [this message]
2024-02-28 16:45 ` dpdklab
2024-02-29 4:52 ` dpdklab
2024-02-29 13:55 ` dpdklab
2024-02-29 13:58 ` dpdklab
2024-02-29 14:02 ` dpdklab
2024-02-29 14:10 ` dpdklab
2024-02-27 19:16 dpdklab
2024-02-27 19:23 dpdklab
2024-02-27 19:27 dpdklab
2024-02-27 19:29 dpdklab
2024-02-27 19:35 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=65df0bcc.d40a0220.0ddd.db96SMTPIN_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).