From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125894-125895 [PATCH] [2/2] event/cnxk: restrict stashing to multi-core
Date: Tue, 11 Apr 2023 16:14:21 +0000 (UTC) [thread overview]
Message-ID: <20230411161421.A22AB60092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125895
_Functional Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tuesday, April 11 2023 07:01:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:65487b12db83c9ef37526a983c43191cd44dae99
125894-125895 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25951/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-11 16:14 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 16:14 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-12 21:32 dpdklab
2023-04-12 21:27 dpdklab
2023-04-11 15:26 dpdklab
2023-04-11 11:16 dpdklab
2023-04-11 11:16 dpdklab
2023-04-11 11:12 dpdklab
2023-04-11 10:24 dpdklab
2023-04-11 10:16 dpdklab
2023-04-11 10:06 dpdklab
2023-04-11 10:05 dpdklab
2023-04-11 10:01 dpdklab
2023-04-11 9:57 dpdklab
2023-04-11 9:55 dpdklab
2023-04-11 9:51 dpdklab
2023-04-11 9:49 dpdklab
2023-04-11 9:46 dpdklab
2023-04-11 9:44 dpdklab
2023-04-11 9:40 dpdklab
2023-04-11 9:40 dpdklab
2023-04-11 9:39 dpdklab
2023-04-11 9:38 dpdklab
2023-04-11 9:35 dpdklab
2023-04-11 9:33 dpdklab
2023-04-11 9:23 dpdklab
2023-04-11 9:21 dpdklab
2023-04-11 9:19 dpdklab
2023-04-11 9:09 dpdklab
2023-04-11 9:05 dpdklab
2023-04-11 9:03 dpdklab
2023-04-11 9:02 dpdklab
2023-04-11 9:00 dpdklab
2023-04-11 8:56 dpdklab
2023-04-11 8:56 dpdklab
2023-04-11 8:50 dpdklab
2023-04-11 8:49 dpdklab
2023-04-11 8:48 dpdklab
2023-04-11 8:47 dpdklab
2023-04-11 8:44 dpdklab
2023-04-11 8:43 dpdklab
2023-04-11 8:37 dpdklab
2023-04-11 8:36 dpdklab
2023-04-11 8:35 dpdklab
2023-04-11 8:34 dpdklab
2023-04-11 8:33 dpdklab
2023-04-11 8:31 dpdklab
2023-04-11 8:29 dpdklab
2023-04-11 8:27 dpdklab
2023-04-11 8:20 dpdklab
2023-04-11 8:20 dpdklab
2023-04-11 8:18 dpdklab
2023-04-11 8:17 dpdklab
2023-04-11 8:16 dpdklab
2023-04-11 8:16 dpdklab
2023-04-11 8:12 dpdklab
[not found] <20230411070129.870-2-pbhagavatula@marvell.com>
2023-04-11 6:52 ` |SUCCESS| pw125894-125895 [PATCH 2/2] " qemudev
2023-04-11 6:56 ` qemudev
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=20230411161421.A22AB60092@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).