From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137321-137324 [PATCH] [v4,4/4] hash: add SVE support for
Date: Tue, 27 Feb 2024 04:13:50 -0800 (PST) [thread overview]
Message-ID: <65ddd1fe.050a0220.442a5.4c0bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137324
_Testing PASS_
Submitter: Yoan Picchi <yoan.picchi@arm.com>
Date: Friday, February 23 2024 13:27:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137321-137324 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| Debian 12 (arm) | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29277/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-27 12:13 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 12:13 dpdklab [this message]
[not found] <20240223132701.2872066-5-yoan.picchi@arm.com>
2024-02-28 4:09 ` dpdklab
2024-02-28 4:14 ` dpdklab
2024-02-29 8:05 ` dpdklab
2024-02-29 8:09 ` dpdklab
2024-02-29 8:14 ` dpdklab
2024-02-29 8:20 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 16:47 dpdklab
2024-02-27 16:16 dpdklab
2024-02-27 16:01 dpdklab
2024-02-27 15:58 dpdklab
2024-02-27 15:54 dpdklab
2024-02-27 15:49 dpdklab
2024-02-27 15:47 dpdklab
2024-02-27 15:47 dpdklab
2024-02-27 15:46 dpdklab
2024-02-27 15:45 dpdklab
2024-02-27 15:45 dpdklab
2024-02-27 15:41 dpdklab
2024-02-27 15:33 dpdklab
2024-02-27 15:33 dpdklab
2024-02-27 15:33 dpdklab
2024-02-27 15:33 dpdklab
2024-02-27 15:33 dpdklab
2024-02-27 15:32 dpdklab
2024-02-27 15:32 dpdklab
2024-02-27 15:30 dpdklab
2024-02-27 15:24 dpdklab
2024-02-27 15:24 dpdklab
2024-02-27 15:24 dpdklab
2024-02-27 15:23 dpdklab
2024-02-27 15:23 dpdklab
2024-02-27 15:21 dpdklab
2024-02-27 15:15 dpdklab
2024-02-27 15:13 dpdklab
2024-02-27 15:13 dpdklab
2024-02-27 14:59 dpdklab
2024-02-27 14:58 dpdklab
2024-02-27 14:58 dpdklab
2024-02-27 14:57 dpdklab
2024-02-27 14:54 dpdklab
2024-02-27 14:52 dpdklab
2024-02-27 14:52 dpdklab
2024-02-27 14:51 dpdklab
2024-02-27 14:50 dpdklab
2024-02-27 14:47 dpdklab
2024-02-27 14:44 dpdklab
2024-02-27 14:43 dpdklab
2024-02-27 14:43 dpdklab
2024-02-27 14:34 dpdklab
2024-02-27 14:32 dpdklab
2024-02-27 14:32 dpdklab
2024-02-27 12:56 dpdklab
2024-02-27 12:55 dpdklab
2024-02-27 12:54 dpdklab
2024-02-27 12:53 dpdklab
2024-02-27 12:53 dpdklab
2024-02-27 12:52 dpdklab
2024-02-27 12:36 dpdklab
2024-02-27 12:10 dpdklab
2024-02-27 12:01 dpdklab
2024-02-27 11:51 dpdklab
2024-02-27 11:51 dpdklab
2024-02-27 11:47 dpdklab
2024-02-27 11:44 dpdklab
2024-02-27 11:42 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=65ddd1fe.050a0220.442a5.4c0bSMTPIN_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).