From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138173-138176 [PATCH] [v6,4/4] hash: add SVE support for
Date: Mon, 11 Mar 2024 17:29:23 -0700 (PDT) [thread overview]
Message-ID: <65efa1e3.050a0220.af51d.51b2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240311232112.736613-5-yoan.picchi@arm.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138176
_Functional Testing PASS_
Submitter: Yoan Picchi <yoan.picchi@arm.com>
Date: Monday, March 11 2024 23:21:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a86f381b826660e88794754c41d3aec79ce9b87c
138173-138176 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29506/
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-12 0:29 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240311232112.736613-5-yoan.picchi@arm.com>
2024-03-11 22:58 ` |SUCCESS| pw138173-138176 [PATCH v6 4/4] hash: add SVE support for bulk key lookup qemudev
2024-03-11 23:02 ` qemudev
2024-03-11 23:22 ` |SUCCESS| pw138176 " checkpatch
2024-03-12 0:12 ` |SUCCESS| pw138173-138176 [PATCH] [v6,4/4] hash: add SVE support for dpdklab
2024-03-12 0:12 ` dpdklab
2024-03-12 0:13 ` dpdklab
2024-03-12 0:13 ` dpdklab
2024-03-12 0:13 ` dpdklab
2024-03-12 0:14 ` dpdklab
2024-03-12 0:18 ` dpdklab
2024-03-12 0:18 ` dpdklab
2024-03-12 0:18 ` dpdklab
2024-03-12 0:18 ` dpdklab
2024-03-12 0:19 ` dpdklab
2024-03-12 0:19 ` dpdklab
2024-03-12 0:19 ` dpdklab
2024-03-12 0:19 ` dpdklab
2024-03-12 0:19 ` dpdklab
2024-03-12 0:19 ` dpdklab
2024-03-12 0:19 ` dpdklab
2024-03-12 0:20 ` dpdklab
2024-03-12 0:20 ` dpdklab
2024-03-12 0:20 ` dpdklab
2024-03-12 0:20 ` dpdklab
2024-03-12 0:20 ` dpdklab
2024-03-12 0:20 ` dpdklab
2024-03-12 0:21 ` dpdklab
2024-03-12 0:21 ` dpdklab
2024-03-12 0:21 ` dpdklab
2024-03-12 0:21 ` dpdklab
2024-03-12 0:21 ` dpdklab
2024-03-12 0:22 ` dpdklab
2024-03-12 0:22 ` dpdklab
2024-03-12 0:22 ` dpdklab
2024-03-12 0:22 ` |SUCCESS| pw138176 [PATCH v6 4/4] hash: add SVE support for bulk key lookup 0-day Robot
2024-03-12 0:22 ` |SUCCESS| pw138173-138176 [PATCH] [v6,4/4] hash: add SVE support for dpdklab
2024-03-12 0:25 ` dpdklab
2024-03-12 0:26 ` dpdklab
2024-03-12 0:26 ` dpdklab
2024-03-12 0:27 ` dpdklab
2024-03-12 0:28 ` dpdklab
2024-03-12 0:28 ` dpdklab
2024-03-12 0:28 ` dpdklab
2024-03-12 0:28 ` dpdklab
2024-03-12 0:29 ` dpdklab
2024-03-12 0:29 ` dpdklab
2024-03-12 0:29 ` dpdklab [this message]
2024-03-12 0:29 ` dpdklab
2024-03-12 0:29 ` dpdklab
2024-03-12 0:29 ` dpdklab
2024-03-12 0:30 ` dpdklab
2024-03-12 0:30 ` dpdklab
2024-03-12 0:30 ` dpdklab
2024-03-12 0:30 ` dpdklab
2024-03-12 0:31 ` dpdklab
2024-03-12 0:31 ` dpdklab
2024-03-12 0:31 ` dpdklab
2024-03-12 0:31 ` dpdklab
2024-03-12 0:31 ` dpdklab
2024-03-12 0:31 ` dpdklab
2024-03-12 0:32 ` dpdklab
2024-03-12 0:32 ` dpdklab
2024-03-12 0:32 ` dpdklab
2024-03-12 0:33 ` dpdklab
2024-03-12 0:33 ` dpdklab
2024-03-12 0:34 ` dpdklab
2024-03-12 0:34 ` dpdklab
2024-03-12 0:35 ` dpdklab
2024-03-12 0:49 ` dpdklab
2024-03-12 0:50 ` dpdklab
2024-03-12 0:51 ` dpdklab
2024-03-12 1:14 ` dpdklab
2024-03-12 1:14 ` dpdklab
2024-03-12 1:15 ` dpdklab
2024-03-12 1:40 ` dpdklab
2024-03-15 7:17 ` dpdklab
2024-03-15 8:02 ` 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=65efa1e3.050a0220.af51d.51b2SMTPIN_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).