From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135751 [PATCH] app/test-crypto-perf: add throughput OOP
Date: Fri, 05 Jan 2024 11:23:35 -0800 (PST) [thread overview]
Message-ID: <65985737.6b0a0220.ed171.596eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135751
_Testing PASS_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Friday, January 05 2024 10:01:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135751 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Debian Bullseye | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28803/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-05 19:23 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 19:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-05 23:55 dpdklab
2024-01-05 22:57 dpdklab
2024-01-05 22:51 dpdklab
2024-01-05 22:39 dpdklab
2024-01-05 22:39 dpdklab
2024-01-05 22:32 dpdklab
2024-01-05 22:26 dpdklab
2024-01-05 22:14 dpdklab
2024-01-05 22:08 dpdklab
2024-01-05 22:08 dpdklab
2024-01-05 21:47 dpdklab
2024-01-05 21:46 dpdklab
2024-01-05 21:41 dpdklab
2024-01-05 21:40 dpdklab
2024-01-05 21:39 dpdklab
2024-01-05 21:37 dpdklab
2024-01-05 21:37 dpdklab
2024-01-05 21:36 dpdklab
2024-01-05 21:35 dpdklab
2024-01-05 21:34 dpdklab
2024-01-05 21:33 dpdklab
2024-01-05 21:31 dpdklab
2024-01-05 21:28 dpdklab
2024-01-05 21:23 dpdklab
2024-01-05 21:21 dpdklab
2024-01-05 21:19 dpdklab
2024-01-05 21:10 dpdklab
2024-01-05 21:09 dpdklab
2024-01-05 20:30 dpdklab
2024-01-05 20:30 dpdklab
2024-01-05 20:27 dpdklab
2024-01-05 20:23 dpdklab
2024-01-05 20:23 dpdklab
2024-01-05 20:21 dpdklab
2024-01-05 20:21 dpdklab
2024-01-05 20:01 dpdklab
2024-01-05 19:57 dpdklab
2024-01-05 19:55 dpdklab
2024-01-05 19:54 dpdklab
2024-01-05 19:52 dpdklab
2024-01-05 19:48 dpdklab
2024-01-05 19:48 dpdklab
2024-01-05 19:47 dpdklab
2024-01-05 19:47 dpdklab
2024-01-05 19:47 dpdklab
2024-01-05 19:46 dpdklab
2024-01-05 19:45 dpdklab
2024-01-05 19:44 dpdklab
2024-01-05 19:44 dpdklab
2024-01-05 19:42 dpdklab
2024-01-05 19:32 dpdklab
2024-01-05 19:32 dpdklab
2024-01-05 19:24 dpdklab
2024-01-05 19:24 dpdklab
2024-01-05 19:23 dpdklab
2024-01-05 19:16 dpdklab
2024-01-05 19:15 dpdklab
2024-01-05 19:11 dpdklab
2024-01-05 19:07 dpdklab
2024-01-05 19:05 dpdklab
2024-01-05 19:00 dpdklab
2024-01-05 18:47 dpdklab
2024-01-05 18:16 dpdklab
2024-01-05 18:11 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=65985737.6b0a0220.ed171.596eSMTPIN_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).