From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137373 [PATCH] [v2] lib/hash: add siphash
Date: Tue, 27 Feb 2024 20:22:28 -0800 (PST) [thread overview]
Message-ID: <65deb504.050a0220.6aef5.c661SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227191437.346593-2-stephen@networkplumber.org>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137373
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, February 27 2024 19:14:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137373 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| Debian 12 (arm) | PASS |
+-----------------+----------------+
| Fedora 38 | PASS |
+-----------------+----------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29300/
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-28 4:22 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227191437.346593-2-stephen@networkplumber.org>
2024-02-27 19:10 ` |SUCCESS| pw137373 [PATCH v2] " qemudev
2024-02-27 19:15 ` qemudev
2024-02-27 19:16 ` checkpatch
2024-02-27 20:06 ` |FAILURE| " 0-day Robot
2024-02-28 2:34 ` |SUCCESS| pw137373 [PATCH] [v2] " dpdklab
2024-02-28 2:38 ` dpdklab
2024-02-28 2:40 ` dpdklab
2024-02-28 2:55 ` dpdklab
2024-02-28 3:02 ` dpdklab
2024-02-28 3:05 ` dpdklab
2024-02-28 3:05 ` dpdklab
2024-02-28 3:33 ` dpdklab
2024-02-28 3:34 ` dpdklab
2024-02-28 3:35 ` dpdklab
2024-02-28 3:42 ` dpdklab
2024-02-28 3:47 ` dpdklab
2024-02-28 3:51 ` dpdklab
2024-02-28 4:14 ` dpdklab
2024-02-28 4:21 ` dpdklab
2024-02-28 4:21 ` dpdklab
2024-02-28 4:22 ` dpdklab [this message]
2024-02-28 4:22 ` dpdklab
2024-02-28 4:23 ` dpdklab
2024-02-28 4:24 ` dpdklab
2024-02-28 4:25 ` dpdklab
2024-02-28 4:26 ` dpdklab
2024-02-28 4:27 ` dpdklab
2024-02-28 4:28 ` dpdklab
2024-02-28 4:31 ` dpdklab
2024-02-28 4:35 ` dpdklab
2024-02-28 4:37 ` dpdklab
2024-02-28 6:21 ` dpdklab
2024-02-28 6:22 ` dpdklab
2024-02-28 6:22 ` dpdklab
2024-02-28 6:23 ` dpdklab
2024-02-28 6:23 ` dpdklab
2024-02-28 6:24 ` dpdklab
2024-02-28 6:24 ` dpdklab
2024-02-28 6:25 ` dpdklab
2024-02-28 6:25 ` dpdklab
2024-02-28 6:27 ` dpdklab
2024-02-28 6:28 ` dpdklab
2024-02-28 6:32 ` dpdklab
2024-02-28 6:34 ` dpdklab
2024-02-28 6:34 ` dpdklab
2024-02-28 6:36 ` dpdklab
2024-02-28 6:37 ` dpdklab
2024-02-28 6:38 ` dpdklab
2024-02-28 6:43 ` dpdklab
2024-02-28 6:48 ` dpdklab
2024-02-28 6:52 ` dpdklab
2024-02-28 7:05 ` dpdklab
2024-02-28 7:08 ` dpdklab
2024-02-28 7:12 ` dpdklab
2024-02-28 7:24 ` dpdklab
2024-02-28 7:27 ` dpdklab
2024-02-28 7:33 ` dpdklab
2024-02-28 7:33 ` dpdklab
2024-02-28 7:34 ` dpdklab
2024-02-28 7:34 ` dpdklab
2024-02-28 8:25 ` dpdklab
2024-02-28 11:43 ` dpdklab
2024-02-28 14:11 ` dpdklab
2024-02-28 14:29 ` dpdklab
2024-02-28 22:40 ` dpdklab
2024-02-29 17:18 ` dpdklab
2024-02-29 17:25 ` dpdklab
2024-02-29 17:30 ` dpdklab
2024-02-29 17:34 ` dpdklab
2024-02-29 20:08 ` dpdklab
2024-02-29 20:47 ` dpdklab
2024-02-29 21:13 ` 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=65deb504.050a0220.6aef5.c661SMTPIN_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).