From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136311 [PATCH] event/cnxk: remove unused files
Date: Fri, 02 Feb 2024 04:13:50 -0800 (PST) [thread overview]
Message-ID: <65bcdc7e.050a0220.36510.42adSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136311
_Functional Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Friday, February 02 2024 09:44:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:dc2f10397574f2ad99d1c2a139e5053f777e8f0b
136311 --> 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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29034/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-02 12:13 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 12:13 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-02 19:01 dpdklab
2024-02-02 18:37 dpdklab
2024-02-02 15:30 dpdklab
2024-02-02 13:46 dpdklab
2024-02-02 13:12 dpdklab
2024-02-02 12:56 dpdklab
2024-02-02 12:45 dpdklab
2024-02-02 12:44 dpdklab
2024-02-02 12:42 dpdklab
2024-02-02 12:41 dpdklab
2024-02-02 12:40 dpdklab
2024-02-02 12:39 dpdklab
2024-02-02 12:37 dpdklab
2024-02-02 12:35 dpdklab
2024-02-02 12:34 dpdklab
2024-02-02 12:34 dpdklab
2024-02-02 12:33 dpdklab
2024-02-02 12:33 dpdklab
2024-02-02 12:31 dpdklab
2024-02-02 12:30 dpdklab
2024-02-02 12:30 dpdklab
2024-02-02 12:29 dpdklab
2024-02-02 12:29 dpdklab
2024-02-02 12:29 dpdklab
2024-02-02 12:27 dpdklab
2024-02-02 12:24 dpdklab
2024-02-02 12:23 dpdklab
2024-02-02 12:22 dpdklab
2024-02-02 12:21 dpdklab
2024-02-02 12:21 dpdklab
2024-02-02 12:20 dpdklab
2024-02-02 12:19 dpdklab
2024-02-02 12:19 dpdklab
2024-02-02 12:19 dpdklab
2024-02-02 12:19 dpdklab
2024-02-02 12:18 dpdklab
2024-02-02 12:18 dpdklab
2024-02-02 12:18 dpdklab
2024-02-02 12:18 dpdklab
2024-02-02 12:18 dpdklab
2024-02-02 12:17 dpdklab
2024-02-02 12:17 dpdklab
2024-02-02 12:17 dpdklab
2024-02-02 12:17 dpdklab
2024-02-02 12:17 dpdklab
2024-02-02 12:16 dpdklab
2024-02-02 12:16 dpdklab
2024-02-02 12:16 dpdklab
2024-02-02 12:16 dpdklab
2024-02-02 12:15 dpdklab
2024-02-02 12:15 dpdklab
2024-02-02 12:15 dpdklab
2024-02-02 12:15 dpdklab
2024-02-02 12:14 dpdklab
2024-02-02 12:14 dpdklab
2024-02-02 12:13 dpdklab
2024-02-02 12:13 dpdklab
2024-02-02 12:12 dpdklab
2024-02-02 12:12 dpdklab
2024-02-02 12:11 dpdklab
2024-02-02 12:11 dpdklab
2024-02-02 12:11 dpdklab
2024-02-02 12:10 dpdklab
2024-02-02 12:10 dpdklab
2024-02-02 12:09 dpdklab
2024-02-02 12:08 dpdklab
[not found] <20240202094445.13038-1-pbhagavatula@marvell.com>
2024-02-02 9:21 ` qemudev
2024-02-02 9:25 ` qemudev
2024-02-02 9:46 ` checkpatch
2024-02-02 10:44 ` 0-day Robot
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=65bcdc7e.050a0220.36510.42adSMTPIN_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).