From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Jieqiang Wang <jieqiang.wang@arm.com>
Subject: |SUCCESS| pw132383 [PATCH] [v3] hash: fix SSE comparison
Date: Sat, 07 Oct 2023 21:50:15 -0700 (PDT) [thread overview]
Message-ID: <65223507.810a0220.253af.80caSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132383
_Testing PASS_
Submitter: Jieqiang Wang <jieqiang.wang@arm.com>
Date: Saturday, October 07 2023 07:36:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4dd146e597d81d900140a904e0b3b9feb1b0be6c
132383 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27850/
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-08 4:50 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 4:50 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-08 7:27 dpdklab
2023-10-08 5:42 dpdklab
2023-10-08 5:39 dpdklab
2023-10-08 5:33 dpdklab
2023-10-08 5:32 dpdklab
2023-10-08 5:30 dpdklab
2023-10-08 5:30 dpdklab
2023-10-08 5:30 dpdklab
2023-10-08 5:28 dpdklab
2023-10-08 5:26 dpdklab
2023-10-08 5:24 dpdklab
2023-10-08 5:16 dpdklab
2023-10-08 5:15 dpdklab
2023-10-08 5:14 dpdklab
2023-10-08 5:13 dpdklab
2023-10-08 4:59 dpdklab
2023-10-08 4:49 dpdklab
2023-10-08 4:44 dpdklab
2023-10-08 4:42 dpdklab
2023-10-08 4:41 dpdklab
2023-10-08 4:35 dpdklab
2023-10-08 4:35 dpdklab
2023-10-08 4:34 dpdklab
2023-10-08 4:34 dpdklab
2023-10-08 4:34 dpdklab
2023-10-08 4:33 dpdklab
2023-10-08 4:33 dpdklab
2023-10-08 4:33 dpdklab
2023-10-08 4:32 dpdklab
2023-10-08 4:32 dpdklab
2023-10-08 4:31 dpdklab
2023-10-08 4:25 dpdklab
2023-10-08 4:23 dpdklab
2023-10-08 4:23 dpdklab
2023-10-08 4:23 dpdklab
2023-10-08 4:23 dpdklab
2023-10-08 4:19 dpdklab
2023-10-08 4:05 dpdklab
2023-10-08 4:04 dpdklab
2023-10-08 4:03 dpdklab
2023-10-08 4:00 dpdklab
2023-10-08 3:50 dpdklab
2023-10-08 3:46 dpdklab
2023-10-08 3:44 dpdklab
2023-10-08 3:44 dpdklab
2023-10-08 3:42 dpdklab
[not found] <20231007073634.3458294-1-jieqiang.wang@arm.com>
2023-10-07 7:18 ` |SUCCESS| pw132383 [PATCH v3] " qemudev
2023-10-07 7:22 ` qemudev
2023-10-07 7:38 ` checkpatch
2023-10-07 8:59 ` 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=65223507.810a0220.253af.80caSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=jieqiang.wang@arm.com \
--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).