From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135761 [PATCH] doc: fix test eventdev example commands
Date: Fri, 05 Jan 2024 09:06:55 -0800 (PST) [thread overview]
Message-ID: <6598372f.0d0a0220.ad857.8100SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135761
_Functional Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Friday, January 05 2024 15:54:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135761 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28811/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-05 17:06 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 17:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-06 0:35 dpdklab
2024-01-05 20:02 dpdklab
2024-01-05 18:13 dpdklab
2024-01-05 18:00 dpdklab
2024-01-05 17:59 dpdklab
2024-01-05 17:54 dpdklab
2024-01-05 17:50 dpdklab
2024-01-05 17:50 dpdklab
2024-01-05 17:50 dpdklab
2024-01-05 17:47 dpdklab
2024-01-05 17:46 dpdklab
2024-01-05 17:23 dpdklab
2024-01-05 17:16 dpdklab
2024-01-05 17:16 dpdklab
2024-01-05 17:14 dpdklab
[not found] <20240105155431.5639-1-pbhagavatula@marvell.com>
2024-01-05 15:36 ` qemudev
2024-01-05 15:40 ` qemudev
2024-01-05 15:55 ` checkpatch
2024-01-05 17:12 ` 0-day Robot
2024-01-05 17:11 dpdklab
2024-01-05 17:10 dpdklab
2024-01-05 17:10 dpdklab
2024-01-05 17:10 dpdklab
2024-01-05 17:09 dpdklab
2024-01-05 17:09 dpdklab
2024-01-05 17:06 dpdklab
2024-01-05 17:06 dpdklab
2024-01-05 17:06 dpdklab
2024-01-05 17:06 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:05 dpdklab
2024-01-05 17:04 dpdklab
2024-01-05 17:04 dpdklab
2024-01-05 17:01 dpdklab
2024-01-05 17:01 dpdklab
2024-01-05 17:01 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:59 dpdklab
2024-01-05 16:58 dpdklab
2024-01-05 16:58 dpdklab
2024-01-05 16:58 dpdklab
2024-01-05 16:58 dpdklab
2024-01-05 16:57 dpdklab
2024-01-05 16:57 dpdklab
2024-01-05 16:57 dpdklab
2024-01-05 16:57 dpdklab
2024-01-05 16:57 dpdklab
2024-01-05 16:56 dpdklab
2024-01-05 16:56 dpdklab
2024-01-05 16:55 dpdklab
2024-01-05 16:55 dpdklab
2024-01-05 16:54 dpdklab
2024-01-05 16:53 dpdklab
2024-01-05 16:52 dpdklab
2024-01-05 16:46 dpdklab
2024-01-05 16:46 dpdklab
2024-01-05 16:45 dpdklab
2024-01-05 16:45 dpdklab
2024-01-05 16:45 dpdklab
2024-01-05 16:44 dpdklab
2024-01-05 16:44 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=6598372f.0d0a0220.ad857.8100SMTPIN_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).