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| pw137321-137324 [PATCH] [v4,4/4] hash: add SVE support for
Date: Thu, 29 Feb 2024 00:14:56 -0800 (PST)	[thread overview]
Message-ID: <65e03d00.050a0220.6c77d.25c5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240223132701.2872066-5-yoan.picchi@arm.com>

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

_Functional Testing PASS_

Submitter: Yoan Picchi <yoan.picchi@arm.com>
Date: Friday, February 23 2024 13:27:01 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137321-137324 --> 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/29277/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-29  8:14 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240223132701.2872066-5-yoan.picchi@arm.com>
2024-02-27  5:49 ` |SUCCESS| pw137321-137324 [PATCH v4 4/4] hash: add SVE support for bulk key lookup qemudev
2024-02-27  5:53 ` qemudev
2024-02-27  6:03 ` |WARNING| pw137324 " checkpatch
2024-02-28  1:01 ` |WARNING| pw137321-137324 [PATCH] [v4,4/4] hash: add SVE support for dpdklab
2024-02-28  4:09 ` |SUCCESS| " dpdklab
2024-02-28  4:14 ` dpdklab
2024-02-28  6:39 ` |WARNING| " dpdklab
2024-02-29  8:05 ` |SUCCESS| " dpdklab
2024-02-29  8:09 ` dpdklab
2024-02-29  8:14 ` dpdklab [this message]
2024-02-29  8:20 ` dpdklab
2024-02-27 16:47 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27 16:16 dpdklab
2024-02-27 16:01 dpdklab
2024-02-27 15:58 dpdklab
2024-02-27 15:54 dpdklab
2024-02-27 15:49 dpdklab
2024-02-27 15:47 dpdklab
2024-02-27 15:47 dpdklab
2024-02-27 15:46 dpdklab
2024-02-27 15:45 dpdklab
2024-02-27 15:45 dpdklab
2024-02-27 15:41 dpdklab
2024-02-27 15:33 dpdklab
2024-02-27 15:33 dpdklab
2024-02-27 15:33 dpdklab
2024-02-27 15:33 dpdklab
2024-02-27 15:33 dpdklab
2024-02-27 15:32 dpdklab
2024-02-27 15:32 dpdklab
2024-02-27 15:30 dpdklab
2024-02-27 15:24 dpdklab
2024-02-27 15:24 dpdklab
2024-02-27 15:24 dpdklab
2024-02-27 15:23 dpdklab
2024-02-27 15:23 dpdklab
2024-02-27 15:21 dpdklab
2024-02-27 15:15 dpdklab
2024-02-27 15:13 dpdklab
2024-02-27 15:13 dpdklab
2024-02-27 14:59 dpdklab
2024-02-27 14:58 dpdklab
2024-02-27 14:58 dpdklab
2024-02-27 14:57 dpdklab
2024-02-27 14:54 dpdklab
2024-02-27 14:52 dpdklab
2024-02-27 14:52 dpdklab
2024-02-27 14:51 dpdklab
2024-02-27 14:50 dpdklab
2024-02-27 14:47 dpdklab
2024-02-27 14:44 dpdklab
2024-02-27 14:43 dpdklab
2024-02-27 14:43 dpdklab
2024-02-27 14:34 dpdklab
2024-02-27 14:32 dpdklab
2024-02-27 14:32 dpdklab
2024-02-27 12:56 dpdklab
2024-02-27 12:55 dpdklab
2024-02-27 12:54 dpdklab
2024-02-27 12:53 dpdklab
2024-02-27 12:53 dpdklab
2024-02-27 12:52 dpdklab
2024-02-27 12:36 dpdklab
2024-02-27 12:13 dpdklab
2024-02-27 12:10 dpdklab
2024-02-27 12:01 dpdklab
2024-02-27 11:51 dpdklab
2024-02-27 11:51 dpdklab
2024-02-27 11:47 dpdklab
2024-02-27 11:44 dpdklab
2024-02-27 11:42 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=65e03d00.050a0220.6c77d.25c5SMTPIN_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).