automatic DPDK test reports
 help / color / mirror / Atom feed
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| pw126251 [PATCH] [v4] mempool: optimize get objects with constant n
Date: Tue, 18 Apr 2023 22:18:28 +0000 (UTC)	[thread overview]
Message-ID: <20230418221828.86A5160095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/126251

_Functional Testing PASS_

Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Tuesday, April 18 2023 20:09:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd

126251 --> functional testing pass

Test environment and result as below:

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/26042/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-04-18 22:18 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 22:18 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-19 13:22 dpdklab
2023-04-19 13:22 dpdklab
2023-04-19 12:48 dpdklab
2023-04-19 12:48 dpdklab
2023-04-19 10:26 dpdklab
2023-04-19  9:32 dpdklab
2023-04-19  9:00 dpdklab
2023-04-19  8:26 dpdklab
2023-04-19  0:30 dpdklab
2023-04-19  0:25 dpdklab
2023-04-19  0:24 dpdklab
2023-04-19  0:15 dpdklab
2023-04-19  0:13 dpdklab
2023-04-19  0:13 dpdklab
2023-04-19  0:11 dpdklab
2023-04-19  0:08 dpdklab
2023-04-19  0:08 dpdklab
2023-04-19  0:07 dpdklab
2023-04-19  0:04 dpdklab
2023-04-18 23:49 dpdklab
2023-04-18 23:26 dpdklab
2023-04-18 23:26 dpdklab
2023-04-18 23:20 dpdklab
2023-04-18 23:15 dpdklab
2023-04-18 23:08 dpdklab
2023-04-18 23:08 dpdklab
2023-04-18 23:04 dpdklab
2023-04-18 22:55 dpdklab
2023-04-18 22:54 dpdklab
2023-04-18 22:41 dpdklab
2023-04-18 22:36 dpdklab
2023-04-18 22:36 dpdklab
2023-04-18 22:35 dpdklab
2023-04-18 22:32 dpdklab
2023-04-18 22:28 dpdklab
2023-04-18 22:23 dpdklab
2023-04-18 22:23 dpdklab
2023-04-18 22:19 dpdklab
2023-04-18 22:19 dpdklab
2023-04-18 22:16 dpdklab
2023-04-18 22:16 dpdklab
2023-04-18 22:15 dpdklab
2023-04-18 22:13 dpdklab
2023-04-18 22:09 dpdklab
2023-04-18 22:08 dpdklab
2023-04-18 21:56 dpdklab
2023-04-18 21:48 dpdklab
2023-04-18 21:42 dpdklab
2023-04-18 21:39 dpdklab
2023-04-18 21:37 dpdklab
2023-04-18 21:37 dpdklab
2023-04-18 21:36 dpdklab
2023-04-18 21:35 dpdklab
2023-04-18 21:31 dpdklab
2023-04-18 21:30 dpdklab
2023-04-18 21:29 dpdklab
2023-04-18 21:27 dpdklab
2023-04-18 21:22 dpdklab
     [not found] <20230418200924.13290-1-mb@smartsharesystems.com>
2023-04-18 19:57 ` |SUCCESS| pw126251 [PATCH v4] " qemudev
2023-04-18 20:01 ` qemudev
2023-04-18 20:10 ` checkpatch
2023-04-18 21:39 ` 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=20230418221828.86A5160095@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).