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| pw137325-137328 [PATCH] [v4,4/4] hash: add SVE support for
Date: Wed, 28 Feb 2024 23:50:06 -0800 (PST)	[thread overview]
Message-ID: <65e0372e.c80a0220.4ae30.1cc7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240226170203.2881280-5-yoan.picchi@arm.com>

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

_Functional Testing PASS_

Submitter: Yoan Picchi <yoan.picchi@arm.com>
Date: Monday, February 26 2024 17:02:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137325-137328 --> 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


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

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  7:52 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240226170203.2881280-5-yoan.picchi@arm.com>
2024-02-27  5:41 ` |SUCCESS| pw137325-137328 [PATCH v4 4/4] hash: add SVE support for bulk key lookup qemudev
2024-02-27  5:46 ` qemudev
2024-02-27  6:10 ` |WARNING| pw137328 " checkpatch
2024-02-27 20:41 ` |SUCCESS| pw137325-137328 [PATCH] [v4,4/4] hash: add SVE support for dpdklab
2024-02-28  4:03 ` dpdklab
2024-02-28  4:22 ` dpdklab
2024-02-29  7:48 ` dpdklab
2024-02-29  7:50 ` dpdklab [this message]
2024-02-29  7:53 ` dpdklab
2024-02-29  7:57 ` dpdklab
2024-02-27 16:01 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27 15:41 dpdklab
2024-02-27 15:23 dpdklab
2024-02-27 15:21 dpdklab
2024-02-27 15:12 dpdklab
2024-02-27 15:12 dpdklab
2024-02-27 14:58 dpdklab
2024-02-27 14:58 dpdklab
2024-02-27 14:57 dpdklab
2024-02-27 14:52 dpdklab
2024-02-27 14:49 dpdklab
2024-02-27 14:48 dpdklab
2024-02-27 14:43 dpdklab
2024-02-27 14:42 dpdklab
2024-02-27 14:35 dpdklab
2024-02-27 14:32 dpdklab
2024-02-27 14:32 dpdklab
2024-02-27 14:31 dpdklab
2024-02-27 14:30 dpdklab
2024-02-27 14:30 dpdklab
2024-02-27 14:29 dpdklab
2024-02-27 14:29 dpdklab
2024-02-27 14:29 dpdklab
2024-02-27 14:29 dpdklab
2024-02-27 14:29 dpdklab
2024-02-27 14:27 dpdklab
2024-02-27 14:26 dpdklab
2024-02-27 14:26 dpdklab
2024-02-27 14:26 dpdklab
2024-02-27 14:26 dpdklab
2024-02-27 14:25 dpdklab
2024-02-27 14:24 dpdklab
2024-02-27 14:23 dpdklab
2024-02-27 14:23 dpdklab
2024-02-27 14:22 dpdklab
2024-02-27 14:22 dpdklab
2024-02-27 14:21 dpdklab
2024-02-27 14:21 dpdklab
2024-02-27 14:20 dpdklab
2024-02-27 14:19 dpdklab
2024-02-27 14:18 dpdklab
2024-02-27 14:18 dpdklab
2024-02-27 14:17 dpdklab
2024-02-27 14:17 dpdklab
2024-02-27 14:06 dpdklab
2024-02-27 13:52 dpdklab
2024-02-27 13:51 dpdklab
2024-02-27 12:10 dpdklab
2024-02-27 12:09 dpdklab
2024-02-27 12:08 dpdklab
2024-02-27 12:05 dpdklab
2024-02-27 12:05 dpdklab
2024-02-27 12:03 dpdklab
2024-02-27 12:03 dpdklab
2024-02-27 11:57 dpdklab
2024-02-27 11:55 dpdklab
2024-02-27 11:52 dpdklab
2024-02-27 11:44 dpdklab
2024-02-27 11:42 dpdklab
2024-02-27 11:37 dpdklab
2024-02-27 11:37 dpdklab
2024-02-27 11:37 dpdklab
2024-02-27 11:31 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=65e0372e.c80a0220.4ae30.1cc7SMTPIN_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).