From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142840 [PATCH] [v6] lib/hash: add siphash
Date: Thu, 01 Aug 2024 15:10:23 -0700 (PDT) [thread overview]
Message-ID: <66ac07cf.050a0220.108c2.11efSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240801153130.63407-1-stephen@networkplumber.org>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/142840
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, August 01 2024 15:31:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3
142840 --> testing pass
Upstream job id: Windows-Compile-DPDK-Mingw64#21221
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | PASS |
+---------------------+--------------------+----------------------+
| FreeBSD 13.3 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 14.1 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
FreeBSD 14.1
Kernel: 14.1
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30699/
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-08-01 22:10 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240801153130.63407-1-stephen@networkplumber.org>
2024-08-01 15:17 ` |SUCCESS| pw142840 [PATCH v6] " qemudev
2024-08-01 15:22 ` qemudev
2024-08-01 15:32 ` checkpatch
2024-08-01 17:22 ` 0-day Robot
2024-08-01 19:27 ` |SUCCESS| pw142840 [PATCH] [v6] " dpdklab
2024-08-01 19:57 ` |PENDING| " dpdklab
2024-08-01 20:02 ` dpdklab
2024-08-01 20:05 ` dpdklab
2024-08-01 20:09 ` |SUCCESS| " dpdklab
2024-08-01 20:13 ` |PENDING| " dpdklab
2024-08-01 20:15 ` |SUCCESS| " dpdklab
2024-08-01 20:17 ` |PENDING| " dpdklab
2024-08-01 20:20 ` dpdklab
2024-08-01 20:22 ` dpdklab
2024-08-01 20:24 ` dpdklab
2024-08-01 20:25 ` dpdklab
2024-08-01 20:26 ` |SUCCESS| " dpdklab
2024-08-01 20:27 ` |PENDING| " dpdklab
2024-08-01 20:30 ` dpdklab
2024-08-01 20:31 ` dpdklab
2024-08-01 20:33 ` dpdklab
2024-08-01 20:34 ` |SUCCESS| " dpdklab
2024-08-01 20:38 ` |PENDING| " dpdklab
2024-08-01 20:46 ` |SUCCESS| " dpdklab
2024-08-01 21:12 ` dpdklab
2024-08-01 21:14 ` dpdklab
2024-08-01 21:18 ` dpdklab
2024-08-01 21:20 ` dpdklab
2024-08-01 21:38 ` dpdklab
2024-08-01 21:43 ` dpdklab
2024-08-01 21:47 ` |PENDING| " dpdklab
2024-08-01 21:47 ` dpdklab
2024-08-01 21:56 ` |SUCCESS| " dpdklab
2024-08-01 21:59 ` |PENDING| " dpdklab
2024-08-01 22:01 ` dpdklab
2024-08-01 22:02 ` dpdklab
2024-08-01 22:08 ` dpdklab
2024-08-01 22:08 ` dpdklab
2024-08-01 22:09 ` |SUCCESS| " dpdklab
2024-08-01 22:10 ` dpdklab [this message]
2024-08-01 22:15 ` dpdklab
2024-08-01 23:45 ` |PENDING| " dpdklab
2024-08-01 23:46 ` dpdklab
2024-08-01 23:47 ` dpdklab
2024-08-01 23:47 ` dpdklab
2024-08-01 23:52 ` dpdklab
2024-08-01 23:54 ` dpdklab
2024-08-01 23:57 ` dpdklab
2024-08-01 23:59 ` dpdklab
2024-08-02 0:00 ` dpdklab
2024-08-02 0:01 ` dpdklab
2024-08-02 0:02 ` dpdklab
2024-08-02 0:08 ` dpdklab
2024-08-02 0:10 ` dpdklab
2024-08-02 0:10 ` dpdklab
2024-08-02 0:11 ` dpdklab
2024-08-02 0:15 ` dpdklab
2024-08-02 0:17 ` dpdklab
2024-08-02 0:20 ` dpdklab
2024-08-02 0:22 ` dpdklab
2024-08-02 0:23 ` dpdklab
2024-08-02 0:29 ` dpdklab
2024-08-02 0:29 ` dpdklab
2024-08-02 0:30 ` dpdklab
2024-08-02 0:32 ` dpdklab
2024-08-02 0:33 ` dpdklab
2024-08-02 0:34 ` dpdklab
2024-08-02 0:34 ` dpdklab
2024-08-02 0:35 ` dpdklab
2024-08-02 0:35 ` |SUCCESS| " dpdklab
2024-08-02 0:39 ` |PENDING| " dpdklab
2024-08-02 0:39 ` dpdklab
2024-08-02 0:40 ` dpdklab
2024-08-02 0:41 ` dpdklab
2024-08-02 0:43 ` dpdklab
2024-08-02 0:43 ` dpdklab
2024-08-02 0:44 ` dpdklab
2024-08-02 0:47 ` dpdklab
2024-08-02 0:48 ` dpdklab
2024-08-02 0:49 ` dpdklab
2024-08-02 0:51 ` |SUCCESS| " dpdklab
2024-08-02 0:52 ` |PENDING| " dpdklab
2024-08-02 0:53 ` dpdklab
2024-08-02 0:53 ` dpdklab
2024-08-02 0:55 ` dpdklab
2024-08-02 1:24 ` dpdklab
2024-08-02 1:24 ` dpdklab
2024-08-02 1:26 ` dpdklab
2024-08-02 1:29 ` dpdklab
2024-08-02 1:38 ` dpdklab
2024-08-02 1:43 ` dpdklab
2024-08-02 1:44 ` dpdklab
2024-08-02 1:48 ` dpdklab
2024-08-02 1:51 ` dpdklab
2024-08-02 1:51 ` dpdklab
2024-08-02 1:55 ` dpdklab
2024-08-02 1:56 ` dpdklab
2024-08-02 1:57 ` dpdklab
2024-08-02 1:57 ` dpdklab
2024-08-02 1:58 ` dpdklab
2024-08-02 2:02 ` dpdklab
2024-08-02 2:02 ` dpdklab
2024-08-02 2:06 ` dpdklab
2024-08-02 2:06 ` dpdklab
2024-08-02 2:19 ` dpdklab
2024-08-02 2:22 ` dpdklab
2024-08-02 2:25 ` |SUCCESS| " dpdklab
2024-08-02 2:33 ` dpdklab
2024-08-02 3:32 ` dpdklab
2024-08-03 1:38 ` dpdklab
2024-08-06 3:38 ` dpdklab
2024-08-06 3:46 ` dpdklab
2024-08-06 3:59 ` 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=66ac07cf.050a0220.108c2.11efSMTPIN_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).