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
Subject: |SUCCESS| pw138220-138223 [PATCH] [v7,4/4] hash: add SVE support for
Date: Tue, 12 Mar 2024 11:18:56 -0700 (PDT)	[thread overview]
Message-ID: <65f09c90.4a0a0220.951ad.e850SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240312154215.802374-5-yoan.picchi@arm.com>

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

_Functional Testing PASS_

Submitter: Yoan Picchi <yoan.picchi@arm.com>
Date: Tuesday, March 12 2024 15:42:15 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a86f381b826660e88794754c41d3aec79ce9b87c

138220-138223 --> functional testing pass

Test environment and result as below:

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


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


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29520/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-12 18:19 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240312154215.802374-5-yoan.picchi@arm.com>
2024-03-12 15:19 ` |SUCCESS| pw138220-138223 [PATCH v7 4/4] hash: add SVE support for bulk key lookup qemudev
2024-03-12 15:24 ` qemudev
2024-03-12 15:43 ` |SUCCESS| pw138223 " checkpatch
2024-03-12 16:42 ` 0-day Robot
2024-03-12 17:58 ` |SUCCESS| pw138220-138223 [PATCH] [v7,4/4] hash: add SVE support for dpdklab
2024-03-12 17:59 ` dpdklab
2024-03-12 17:59 ` dpdklab
2024-03-12 18:00 ` dpdklab
2024-03-12 18:15 ` dpdklab
2024-03-12 18:16 ` dpdklab
2024-03-12 18:17 ` dpdklab
2024-03-12 18:18 ` dpdklab
2024-03-12 18:18 ` dpdklab
2024-03-12 18:18 ` dpdklab [this message]
2024-03-12 18:19 ` dpdklab
2024-03-12 18:19 ` dpdklab
2024-03-12 18:20 ` dpdklab
2024-03-12 18:20 ` dpdklab
2024-03-12 18:21 ` dpdklab
2024-03-12 18:21 ` dpdklab
2024-03-12 18:22 ` dpdklab
2024-03-12 18:25 ` dpdklab
2024-03-12 18:25 ` dpdklab
2024-03-12 18:25 ` dpdklab
2024-03-12 18:26 ` dpdklab
2024-03-12 18:26 ` dpdklab
2024-03-12 18:26 ` dpdklab
2024-03-12 18:31 ` dpdklab
2024-03-12 18:31 ` dpdklab
2024-03-12 18:32 ` dpdklab
2024-03-12 18:32 ` dpdklab
2024-03-12 18:33 ` dpdklab
2024-03-12 18:33 ` dpdklab
2024-03-12 18:34 ` dpdklab
2024-03-12 18:34 ` dpdklab
2024-03-12 18:36 ` dpdklab
2024-03-12 18:37 ` dpdklab
2024-03-12 18:38 ` dpdklab
2024-03-12 18:38 ` dpdklab
2024-03-12 18:39 ` dpdklab
2024-03-12 18:39 ` dpdklab
2024-03-12 18:40 ` dpdklab
2024-03-12 18:40 ` dpdklab
2024-03-12 18:41 ` dpdklab
2024-03-12 18:41 ` dpdklab
2024-03-12 18:42 ` dpdklab
2024-03-12 18:42 ` dpdklab
2024-03-12 18:43 ` dpdklab
2024-03-12 18:46 ` dpdklab
2024-03-12 18:55 ` dpdklab
2024-03-12 18:56 ` dpdklab
2024-03-12 18:56 ` dpdklab
2024-03-12 18:57 ` dpdklab
2024-03-12 18:58 ` dpdklab
2024-03-12 18:58 ` dpdklab
2024-03-12 18:58 ` dpdklab
2024-03-12 18:58 ` dpdklab
2024-03-12 18:59 ` dpdklab
2024-03-12 19:00 ` dpdklab
2024-03-12 19:00 ` dpdklab
2024-03-12 19:00 ` dpdklab
2024-03-12 19:00 ` dpdklab
2024-03-12 19:01 ` dpdklab
2024-03-12 19:02 ` dpdklab
2024-03-12 19:07 ` dpdklab
2024-03-12 19:08 ` dpdklab
2024-03-12 19:08 ` dpdklab
2024-03-12 19:12 ` dpdklab
2024-03-12 19:13 ` dpdklab
2024-03-12 19:14 ` dpdklab
2024-03-12 19:14 ` dpdklab
2024-03-12 19:15 ` dpdklab
2024-03-12 20:13 ` dpdklab
2024-03-12 21:29 ` dpdklab
2024-03-16  4:51 ` dpdklab
2024-03-16  5:49 ` 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=65f09c90.4a0a0220.951ad.e850SMTPIN_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).