From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132462 [PATCH] [v2] ethdev: add calculate hash function
Date: Tue, 10 Oct 2023 18:21:03 -0700 (PDT) [thread overview]
Message-ID: <6525f87f.920a0220.5b35e.a70cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132462
_Testing PASS_
Submitter: Ori Kam <orika@nvidia.com>
Date: Tuesday, October 10 2023 14:24:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4dd146e597d81d900140a904e0b3b9feb1b0be6c
132462 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| FreeBSD 13 | PASS |
+---------------------+--------------------+
| Windows Server 2019 | PASS |
+---------------------+--------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27881/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-11 1:21 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 1:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-12 2:54 dpdklab
2023-10-12 2:52 dpdklab
2023-10-12 2:52 dpdklab
2023-10-12 2:39 dpdklab
2023-10-12 1:28 dpdklab
2023-10-11 10:38 dpdklab
2023-10-11 3:56 dpdklab
2023-10-11 3:22 dpdklab
2023-10-11 3:21 dpdklab
2023-10-11 3:21 dpdklab
2023-10-11 3:19 dpdklab
2023-10-11 3:18 dpdklab
2023-10-11 3:03 dpdklab
2023-10-11 3:01 dpdklab
2023-10-11 3:00 dpdklab
2023-10-11 2:57 dpdklab
2023-10-11 2:57 dpdklab
2023-10-11 2:56 dpdklab
2023-10-11 2:56 dpdklab
2023-10-11 2:55 dpdklab
2023-10-11 2:55 dpdklab
2023-10-11 2:55 dpdklab
2023-10-11 2:54 dpdklab
2023-10-11 2:54 dpdklab
2023-10-11 2:47 dpdklab
2023-10-11 2:47 dpdklab
2023-10-11 2:46 dpdklab
2023-10-11 2:45 dpdklab
2023-10-11 2:44 dpdklab
2023-10-11 2:43 dpdklab
2023-10-11 2:42 dpdklab
2023-10-11 2:41 dpdklab
2023-10-11 2:40 dpdklab
2023-10-11 2:37 dpdklab
2023-10-11 2:37 dpdklab
2023-10-11 2:36 dpdklab
2023-10-11 2:35 dpdklab
2023-10-11 2:34 dpdklab
2023-10-11 2:33 dpdklab
2023-10-11 2:31 dpdklab
2023-10-11 1:53 dpdklab
2023-10-11 1:07 dpdklab
2023-10-10 21:24 dpdklab
2023-10-10 21:20 dpdklab
2023-10-10 21:09 dpdklab
2023-10-10 21:03 dpdklab
2023-10-10 20:58 dpdklab
2023-10-10 20:55 dpdklab
2023-10-10 20:54 dpdklab
[not found] <20231010142401.27289-1-orika@nvidia.com>
2023-10-10 14:06 ` |SUCCESS| pw132462 [PATCH v2] " qemudev
2023-10-10 14:10 ` qemudev
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=6525f87f.920a0220.5b35e.a70cSMTPIN_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).