From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139126 [PATCH] [v4] eal/x86: improve rte_memcpy const si
Date: Fri, 05 Apr 2024 08:30:03 -0700 (PDT) [thread overview]
Message-ID: <661018fb.170a0220.c7501.312cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240405134831.47996-1-mb@smartsharesystems.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139126
_Testing PASS_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Friday, April 05 2024 13:48:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139126 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.6
Fedora 39
Kernel: Depends on container host
Compiler: clang 17.0.6
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29724/
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-04-05 15:30 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240405134831.47996-1-mb@smartsharesystems.com>
2024-04-05 13:25 ` |SUCCESS| pw139126 [PATCH v4] eal/x86: improve rte_memcpy const size 16 performance qemudev
2024-04-05 13:30 ` qemudev
2024-04-05 13:50 ` checkpatch
2024-04-05 14:29 ` |SUCCESS| pw139126 [PATCH] [v4] eal/x86: improve rte_memcpy const si dpdklab
2024-04-05 14:29 ` dpdklab
2024-04-05 14:30 ` dpdklab
2024-04-05 14:31 ` dpdklab
2024-04-05 14:44 ` |SUCCESS| pw139126 [PATCH v4] eal/x86: improve rte_memcpy const size 16 performance 0-day Robot
2024-04-05 14:48 ` |SUCCESS| pw139126 [PATCH] [v4] eal/x86: improve rte_memcpy const si dpdklab
2024-04-05 14:48 ` dpdklab
2024-04-05 14:48 ` dpdklab
2024-04-05 14:49 ` dpdklab
2024-04-05 14:49 ` |WARNING| " dpdklab
2024-04-05 14:49 ` |SUCCESS| " dpdklab
2024-04-05 14:50 ` dpdklab
2024-04-05 14:50 ` dpdklab
2024-04-05 14:50 ` dpdklab
2024-04-05 14:51 ` dpdklab
2024-04-05 14:51 ` dpdklab
2024-04-05 14:51 ` dpdklab
2024-04-05 14:52 ` dpdklab
2024-04-05 14:52 ` dpdklab
2024-04-05 14:56 ` |WARNING| " dpdklab
2024-04-05 14:57 ` dpdklab
2024-04-05 14:57 ` |SUCCESS| " dpdklab
2024-04-05 14:57 ` |WARNING| " dpdklab
2024-04-05 14:58 ` dpdklab
2024-04-05 14:58 ` |SUCCESS| " dpdklab
2024-04-05 14:58 ` dpdklab
2024-04-05 14:58 ` dpdklab
2024-04-05 14:59 ` dpdklab
2024-04-05 14:59 ` dpdklab
2024-04-05 14:59 ` dpdklab
2024-04-05 15:00 ` dpdklab
2024-04-05 15:00 ` dpdklab
2024-04-05 15:00 ` |WARNING| " dpdklab
2024-04-05 15:00 ` |SUCCESS| " dpdklab
2024-04-05 15:00 ` dpdklab
2024-04-05 15:00 ` dpdklab
2024-04-05 15:01 ` dpdklab
2024-04-05 15:01 ` dpdklab
2024-04-05 15:02 ` dpdklab
2024-04-05 15:02 ` |WARNING| " dpdklab
2024-04-05 15:02 ` |SUCCESS| " dpdklab
2024-04-05 15:02 ` dpdklab
2024-04-05 15:02 ` dpdklab
2024-04-05 15:03 ` dpdklab
2024-04-05 15:03 ` dpdklab
2024-04-05 15:03 ` |WARNING| " dpdklab
2024-04-05 15:03 ` |SUCCESS| " dpdklab
2024-04-05 15:08 ` dpdklab
2024-04-05 15:21 ` dpdklab
2024-04-05 15:22 ` dpdklab
2024-04-05 15:23 ` dpdklab
2024-04-05 15:23 ` dpdklab
2024-04-05 15:24 ` dpdklab
2024-04-05 15:24 ` dpdklab
2024-04-05 15:24 ` dpdklab
2024-04-05 15:25 ` dpdklab
2024-04-05 15:26 ` |WARNING| " dpdklab
2024-04-05 15:26 ` dpdklab
2024-04-05 15:26 ` |SUCCESS| " dpdklab
2024-04-05 15:26 ` dpdklab
2024-04-05 15:27 ` |WARNING| " dpdklab
2024-04-05 15:28 ` |SUCCESS| " dpdklab
2024-04-05 15:30 ` dpdklab [this message]
2024-04-05 15:30 ` |WARNING| " dpdklab
2024-04-05 15:34 ` dpdklab
2024-04-05 15:35 ` dpdklab
2024-04-05 15:36 ` |SUCCESS| " dpdklab
2024-04-05 15:36 ` |WARNING| " dpdklab
2024-04-05 15:36 ` |SUCCESS| " dpdklab
2024-04-05 15:36 ` dpdklab
2024-04-05 15:38 ` dpdklab
2024-04-05 15:38 ` |WARNING| " dpdklab
2024-04-05 15:38 ` |SUCCESS| " dpdklab
2024-04-05 15:38 ` |WARNING| " dpdklab
2024-04-05 15:48 ` |SUCCESS| " dpdklab
2024-04-05 15:48 ` |WARNING| " dpdklab
2024-04-05 15:51 ` dpdklab
2024-04-05 15:52 ` |SUCCESS| " dpdklab
2024-04-05 15:53 ` |WARNING| " dpdklab
2024-04-05 16:04 ` |SUCCESS| " dpdklab
2024-04-05 16:08 ` dpdklab
2024-04-05 16:10 ` 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=661018fb.170a0220.c7501.312cSMTPIN_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).