From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137410 [PATCH] [v2] app/eventdev: support DMA adapter te
Date: Wed, 28 Feb 2024 00:03:56 -0800 (PST) [thread overview]
Message-ID: <65dee8ec.250a0220.28feeb.3baaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228060102.4137229-1-amitprakashs@marvell.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137410
_Functional Testing PASS_
Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Wednesday, February 28 2024 06:01:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:850a57695b4647f62f31019baa8a92bcd3ff3531
137410 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29307/
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 8:03 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240228060102.4137229-1-amitprakashs@marvell.com>
2024-02-28 5:38 ` |SUCCESS| pw137410 [PATCH v2] app/eventdev: support DMA adapter test qemudev
2024-02-28 5:43 ` qemudev
2024-02-28 6:01 ` checkpatch
2024-02-28 7:05 ` 0-day Robot
2024-02-28 7:41 ` |SUCCESS| pw137410 [PATCH] [v2] app/eventdev: support DMA adapter te dpdklab
2024-02-28 7:42 ` dpdklab
2024-02-28 7:43 ` dpdklab
2024-02-28 7:52 ` dpdklab
2024-02-28 8:03 ` dpdklab [this message]
2024-02-28 8:05 ` dpdklab
2024-02-28 8:06 ` dpdklab
2024-02-28 8:07 ` dpdklab
2024-02-28 8:08 ` dpdklab
2024-02-28 8:09 ` dpdklab
2024-02-28 8:09 ` dpdklab
2024-02-28 8:10 ` dpdklab
2024-02-28 8:10 ` dpdklab
2024-02-28 8:11 ` dpdklab
2024-02-28 8:12 ` dpdklab
2024-02-28 8:12 ` dpdklab
2024-02-28 8:14 ` dpdklab
2024-02-28 8:14 ` dpdklab
2024-02-28 8:15 ` dpdklab
2024-02-28 8:15 ` dpdklab
2024-02-28 8:16 ` dpdklab
2024-02-28 8:23 ` dpdklab
2024-02-28 8:23 ` dpdklab
2024-02-28 8:23 ` dpdklab
2024-02-28 8:23 ` dpdklab
2024-02-28 8:23 ` dpdklab
2024-02-28 8:24 ` dpdklab
2024-02-28 8:24 ` dpdklab
2024-02-28 8:24 ` dpdklab
2024-02-28 8:24 ` dpdklab
2024-02-28 8:24 ` dpdklab
2024-02-28 8:24 ` dpdklab
2024-02-28 8:25 ` dpdklab
2024-02-28 8:25 ` dpdklab
2024-02-28 8:25 ` dpdklab
2024-02-28 8:25 ` dpdklab
2024-02-28 8:26 ` dpdklab
2024-02-28 8:26 ` dpdklab
2024-02-28 8:27 ` dpdklab
2024-02-28 8:27 ` dpdklab
2024-02-28 8:35 ` dpdklab
2024-02-28 8:36 ` dpdklab
2024-02-28 8:37 ` dpdklab
2024-02-28 8:37 ` dpdklab
2024-02-28 8:37 ` dpdklab
2024-02-28 8:38 ` dpdklab
2024-02-28 8:38 ` dpdklab
2024-02-28 8:44 ` dpdklab
2024-02-28 8:45 ` dpdklab
2024-02-28 8:45 ` dpdklab
2024-02-28 8:48 ` dpdklab
2024-02-28 8:49 ` dpdklab
2024-02-28 8:50 ` dpdklab
2024-02-28 8:51 ` dpdklab
2024-02-28 8:52 ` dpdklab
2024-02-28 8:52 ` dpdklab
2024-02-28 8:56 ` dpdklab
2024-02-28 8:59 ` dpdklab
2024-02-28 9:16 ` dpdklab
2024-02-28 11:13 ` dpdklab
2024-02-28 15:32 ` dpdklab
2024-02-28 16:34 ` dpdklab
2024-02-28 16:43 ` dpdklab
2024-02-29 4:43 ` dpdklab
2024-02-29 19:23 ` dpdklab
2024-02-29 19:25 ` dpdklab
2024-02-29 19:34 ` dpdklab
2024-02-29 19:50 ` dpdklab
2024-03-01 4:06 ` dpdklab
2024-03-01 4:39 ` dpdklab
2024-03-01 5:08 ` 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=65dee8ec.250a0220.28feeb.3baaSMTPIN_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).