From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131183 [PATCH] hash: fix SSE comparison
Date: Tue, 05 Sep 2023 20:21:43 -0700 (PDT) [thread overview]
Message-ID: <64f7f047.6b0a0220.6d1f2.f78bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131183
_Testing PASS_
Submitter: Jieqiang Wang <jieqiang.wang@arm.com>
Date: Wednesday, September 06 2023 02:31:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e92ba1426914db1d224dd5e9a1743657681b8814
131183 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | SKIPPED | PASS |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
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/27531/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-06 3:21 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 3:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 7:37 dpdklab
2023-09-06 7:32 dpdklab
2023-09-06 7:27 dpdklab
2023-09-06 7:23 dpdklab
2023-09-06 4:51 dpdklab
2023-09-06 4:31 dpdklab
2023-09-06 4:25 dpdklab
2023-09-06 4:03 dpdklab
2023-09-06 4:02 dpdklab
2023-09-06 3:57 dpdklab
2023-09-06 3:56 dpdklab
2023-09-06 3:56 dpdklab
2023-09-06 3:56 dpdklab
2023-09-06 3:55 dpdklab
2023-09-06 3:55 dpdklab
2023-09-06 3:51 dpdklab
2023-09-06 3:50 dpdklab
2023-09-06 3:50 dpdklab
2023-09-06 3:42 dpdklab
2023-09-06 3:42 dpdklab
2023-09-06 3:42 dpdklab
2023-09-06 3:38 dpdklab
2023-09-06 3:35 dpdklab
2023-09-06 3:34 dpdklab
2023-09-06 3:33 dpdklab
2023-09-06 3:32 dpdklab
2023-09-06 3:32 dpdklab
2023-09-06 3:32 dpdklab
2023-09-06 3:32 dpdklab
2023-09-06 3:31 dpdklab
2023-09-06 3:31 dpdklab
2023-09-06 3:28 dpdklab
2023-09-06 3:28 dpdklab
2023-09-06 3:27 dpdklab
2023-09-06 3:27 dpdklab
2023-09-06 3:27 dpdklab
2023-09-06 3:27 dpdklab
2023-09-06 3:26 dpdklab
2023-09-06 3:26 dpdklab
2023-09-06 3:26 dpdklab
2023-09-06 3:26 dpdklab
2023-09-06 3:26 dpdklab
2023-09-06 3:25 dpdklab
2023-09-06 3:23 dpdklab
2023-09-06 3:23 dpdklab
2023-09-06 3:22 dpdklab
2023-09-06 3:22 dpdklab
2023-09-06 3:20 dpdklab
2023-09-06 3:20 dpdklab
2023-09-06 3:20 dpdklab
[not found] <20230906023100.3618303-1-jieqiang.wang@arm.com>
2023-09-06 2:18 ` qemudev
2023-09-06 2:22 ` qemudev
2023-09-06 2:32 ` checkpatch
2023-09-06 3:19 ` 0-day Robot
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=64f7f047.6b0a0220.6d1f2.f78bSMTPIN_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).