From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137808 [PATCH] [v7] mempool: test performance with large
Date: Sat, 02 Mar 2024 12:56:53 -0800 (PST) [thread overview]
Message-ID: <65e39295.c80a0220.12c74.0fb3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240302200408.6419-1-mb@smartsharesystems.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137808
_Functional Testing PASS_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Saturday, March 02 2024 20:04:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5df34de5808a7b826b8bc035d6ee3161a12be364
137808 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.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/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29386/
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-03-02 20:56 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240302200408.6419-1-mb@smartsharesystems.com>
2024-03-02 19:40 ` |SUCCESS| pw137808 [PATCH v7] mempool: test performance with larger bursts qemudev
2024-03-02 19:45 ` qemudev
2024-03-02 20:04 ` checkpatch
2024-03-02 20:43 ` |SUCCESS| pw137808 [PATCH] [v7] mempool: test performance with large dpdklab
2024-03-02 20:44 ` dpdklab
2024-03-02 20:45 ` dpdklab
2024-03-02 20:45 ` dpdklab
2024-03-02 20:46 ` dpdklab
2024-03-02 20:46 ` dpdklab
2024-03-02 20:46 ` dpdklab
2024-03-02 20:47 ` dpdklab
2024-03-02 20:47 ` dpdklab
2024-03-02 20:47 ` dpdklab
2024-03-02 20:47 ` dpdklab
2024-03-02 20:47 ` dpdklab
2024-03-02 20:48 ` dpdklab
2024-03-02 20:48 ` dpdklab
2024-03-02 20:49 ` dpdklab
2024-03-02 20:49 ` dpdklab
2024-03-02 20:49 ` dpdklab
2024-03-02 20:50 ` dpdklab
2024-03-02 20:50 ` dpdklab
2024-03-02 20:51 ` dpdklab
2024-03-02 20:51 ` dpdklab
2024-03-02 20:52 ` dpdklab
2024-03-02 20:52 ` dpdklab
2024-03-02 20:52 ` dpdklab
2024-03-02 20:52 ` dpdklab
2024-03-02 20:54 ` dpdklab
2024-03-02 20:54 ` dpdklab
2024-03-02 20:55 ` dpdklab
2024-03-02 20:55 ` dpdklab
2024-03-02 20:55 ` dpdklab
2024-03-02 20:55 ` dpdklab
2024-03-02 20:55 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:56 ` dpdklab [this message]
2024-03-02 20:56 ` dpdklab
2024-03-02 20:56 ` dpdklab
2024-03-02 20:57 ` dpdklab
2024-03-02 20:57 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:58 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 20:59 ` dpdklab
2024-03-02 21:00 ` dpdklab
2024-03-02 21:00 ` dpdklab
2024-03-02 21:00 ` dpdklab
2024-03-02 21:01 ` dpdklab
2024-03-02 21:01 ` dpdklab
2024-03-02 21:01 ` dpdklab
2024-03-02 21:01 ` dpdklab
2024-03-02 21:03 ` dpdklab
2024-03-02 21:04 ` dpdklab
2024-03-02 21:05 ` |SUCCESS| pw137808 [PATCH v7] mempool: test performance with larger bursts 0-day Robot
2024-03-02 21:22 ` |SUCCESS| pw137808 [PATCH] [v7] mempool: test performance with large dpdklab
2024-03-02 21:53 ` dpdklab
2024-03-02 22:00 ` dpdklab
2024-03-02 22:13 ` dpdklab
2024-03-03 6:21 ` dpdklab
2024-03-06 16:15 ` dpdklab
2024-03-06 16:29 ` dpdklab
2024-03-06 17:05 ` 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=65e39295.c80a0220.12c74.0fb3SMTPIN_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).