From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137366-137367 [PATCH] [v5,4/4] hash: add SVE support for
Date: Thu, 29 Feb 2024 00:08:44 -0800 (PST) [thread overview]
Message-ID: <65e03b8c.050a0220.689c1.1a08SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227174203.2889333-5-yoan.picchi@arm.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137367
_Testing PASS_
Submitter: Yoan Picchi <yoan.picchi@arm.com>
Date: Tuesday, February 27 2024 17:42:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137366-137367 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29296/
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-02-29 8:08 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227174203.2889333-5-yoan.picchi@arm.com>
2024-02-27 17:27 ` |SUCCESS| pw137366-137367 [PATCH v5 4/4] hash: add SVE support for bulk key lookup qemudev
2024-02-27 17:32 ` qemudev
2024-02-27 17:44 ` |SUCCESS| pw137367 " checkpatch
2024-02-27 19:05 ` 0-day Robot
2024-02-27 19:55 ` |SUCCESS| pw137366-137367 [PATCH] [v5,4/4] hash: add SVE support for dpdklab
2024-02-27 20:00 ` dpdklab
2024-02-27 20:02 ` dpdklab
2024-02-27 20:14 ` dpdklab
2024-02-27 20:36 ` dpdklab
2024-02-27 20:42 ` dpdklab
2024-02-27 20:43 ` dpdklab
2024-02-27 20:43 ` dpdklab
2024-02-27 20:44 ` dpdklab
2024-02-27 20:45 ` dpdklab
2024-02-27 20:50 ` dpdklab
2024-02-27 20:52 ` dpdklab
2024-02-27 20:53 ` dpdklab
2024-02-27 20:54 ` dpdklab
2024-02-27 21:00 ` dpdklab
2024-02-27 23:44 ` dpdklab
2024-02-27 23:45 ` dpdklab
2024-02-27 23:46 ` dpdklab
2024-02-27 23:49 ` dpdklab
2024-02-27 23:51 ` dpdklab
2024-02-27 23:51 ` dpdklab
2024-02-27 23:57 ` dpdklab
2024-02-27 23:57 ` dpdklab
2024-02-27 23:58 ` dpdklab
2024-02-27 23:59 ` dpdklab
2024-02-27 23:59 ` dpdklab
2024-02-28 0:02 ` dpdklab
2024-02-28 0:03 ` dpdklab
2024-02-28 0:04 ` dpdklab
2024-02-28 0:06 ` dpdklab
2024-02-28 0:06 ` dpdklab
2024-02-28 0:06 ` dpdklab
2024-02-28 0:07 ` dpdklab
2024-02-28 0:10 ` dpdklab
2024-02-28 0:10 ` dpdklab
2024-02-28 0:10 ` dpdklab
2024-02-28 0:11 ` dpdklab
2024-02-28 0:11 ` dpdklab
2024-02-28 0:13 ` dpdklab
2024-02-28 0:15 ` dpdklab
2024-02-28 0:16 ` dpdklab
2024-02-28 0:23 ` dpdklab
2024-02-28 0:24 ` dpdklab
2024-02-28 0:24 ` dpdklab
2024-02-28 0:25 ` dpdklab
2024-02-28 0:26 ` dpdklab
2024-02-28 0:27 ` dpdklab
2024-02-28 0:27 ` dpdklab
2024-02-28 0:31 ` dpdklab
2024-02-28 0:32 ` dpdklab
2024-02-28 0:34 ` dpdklab
2024-02-28 0:34 ` dpdklab
2024-02-28 0:36 ` dpdklab
2024-02-28 0:45 ` dpdklab
2024-02-28 1:20 ` dpdklab
2024-02-28 1:22 ` dpdklab
2024-02-28 3:11 ` dpdklab
2024-02-28 3:20 ` dpdklab
2024-02-28 8:45 ` dpdklab
2024-02-28 10:57 ` dpdklab
2024-02-28 11:16 ` dpdklab
2024-02-28 17:47 ` dpdklab
2024-02-29 8:08 ` dpdklab [this message]
2024-02-29 14:53 ` dpdklab
2024-02-29 14:54 ` dpdklab
2024-02-29 14:59 ` dpdklab
2024-02-29 15:01 ` 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=65e03b8c.050a0220.689c1.1a08SMTPIN_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).