automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142273 [PATCH] [v9] eal/x86: improve rte_memcpy const si
Date: Wed, 10 Jul 2024 10:42:43 -0700 (PDT)	[thread overview]
Message-ID: <668ec813.170a0220.6fa08.797eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240709132735.25671-1-mb@smartsharesystems.com>

Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142273

_Testing pending_

Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Tuesday, July 09 2024 13:27:35 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8e8aa4a4f90dce1fcea03a93f508e3d9bc0c98c0

142273 --> testing pending

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 37           | PEND           |
+---------------------+----------------+
| Fedora 38           | PEND           |
+---------------------+----------------+
| Fedora 38 (Clang)   | PEND           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PEND           |
+---------------------+----------------+
| Fedora 40           | PEND           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| Ubuntu 24.04        | PASS           |
+---------------------+----------------+
| RHEL9               | PASS           |
+---------------------+----------------+


Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

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 12.2.0

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

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

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30480/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-07-10 17:42 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240709132735.25671-1-mb@smartsharesystems.com>
2024-07-09 13:08 ` |SUCCESS| pw142273 [PATCH v9] eal/x86: improve rte_memcpy const size 16 performance qemudev
2024-07-09 13:12 ` qemudev
2024-07-09 13:28 ` checkpatch
2024-07-09 14:42 ` |PENDING| pw142273 [PATCH] [v9] eal/x86: improve rte_memcpy const si dpdklab
2024-07-09 14:43 ` |SUCCESS| pw142273 [PATCH v9] eal/x86: improve rte_memcpy const size 16 performance 0-day Robot
2024-07-09 14:45 ` |SUCCESS| pw142273 [PATCH] [v9] eal/x86: improve rte_memcpy const si dpdklab
2024-07-09 14:50 ` dpdklab
2024-07-09 14:53 ` dpdklab
2024-07-09 14:53 ` dpdklab
2024-07-09 14:59 ` |PENDING| " dpdklab
2024-07-09 15:00 ` dpdklab
2024-07-09 15:01 ` dpdklab
2024-07-09 15:03 ` |SUCCESS| " dpdklab
2024-07-09 15:05 ` |PENDING| " dpdklab
2024-07-09 15:07 ` dpdklab
2024-07-09 15:07 ` |SUCCESS| " dpdklab
2024-07-09 15:14 ` dpdklab
2024-07-09 15:16 ` dpdklab
2024-07-09 15:17 ` dpdklab
2024-07-09 15:20 ` |PENDING| " dpdklab
2024-07-09 15:23 ` dpdklab
2024-07-09 15:29 ` dpdklab
2024-07-09 15:29 ` dpdklab
2024-07-09 15:37 ` |SUCCESS| " dpdklab
2024-07-09 15:50 ` |PENDING| " dpdklab
2024-07-09 15:52 ` dpdklab
2024-07-09 15:53 ` dpdklab
2024-07-09 16:00 ` dpdklab
2024-07-09 16:03 ` dpdklab
2024-07-09 16:11 ` |SUCCESS| " dpdklab
2024-07-09 16:16 ` |PENDING| " dpdklab
2024-07-09 16:20 ` dpdklab
2024-07-09 16:21 ` dpdklab
2024-07-09 16:22 ` dpdklab
2024-07-09 16:22 ` dpdklab
2024-07-09 16:24 ` dpdklab
2024-07-09 16:29 ` dpdklab
2024-07-09 16:32 ` dpdklab
2024-07-09 16:35 ` dpdklab
2024-07-09 16:44 ` |SUCCESS| " dpdklab
2024-07-09 16:46 ` dpdklab
2024-07-09 20:43 ` |PENDING| " dpdklab
2024-07-09 20:45 ` dpdklab
2024-07-09 20:53 ` dpdklab
2024-07-09 20:58 ` dpdklab
2024-07-09 21:00 ` dpdklab
2024-07-10  1:28 ` dpdklab
2024-07-10  1:35 ` dpdklab
2024-07-10  1:37 ` dpdklab
2024-07-10  1:42 ` dpdklab
2024-07-10  1:49 ` dpdklab
2024-07-10  3:09 ` |SUCCESS| " dpdklab
2024-07-10  3:45 ` |PENDING| " dpdklab
2024-07-10  3:47 ` dpdklab
2024-07-10  4:02 ` dpdklab
2024-07-10  4:07 ` dpdklab
2024-07-10  4:09 ` dpdklab
2024-07-10  4:14 ` dpdklab
2024-07-10  4:16 ` dpdklab
2024-07-10  4:17 ` dpdklab
2024-07-10  4:19 ` dpdklab
2024-07-10  4:19 ` |SUCCESS| " dpdklab
2024-07-10  4:28 ` |PENDING| " dpdklab
2024-07-10  4:29 ` dpdklab
2024-07-10  4:31 ` dpdklab
2024-07-10  4:32 ` |SUCCESS| " dpdklab
2024-07-10  4:34 ` |PENDING| " dpdklab
2024-07-10  4:34 ` dpdklab
2024-07-10  4:39 ` dpdklab
2024-07-10  4:39 ` dpdklab
2024-07-10  4:40 ` dpdklab
2024-07-10  4:44 ` dpdklab
2024-07-10  4:44 ` dpdklab
2024-07-10  4:46 ` dpdklab
2024-07-10  4:48 ` dpdklab
2024-07-10  4:50 ` dpdklab
2024-07-10  4:55 ` dpdklab
2024-07-10  4:55 ` dpdklab
2024-07-10  4:55 ` dpdklab
2024-07-10  4:56 ` dpdklab
2024-07-10  4:56 ` dpdklab
2024-07-10  5:04 ` dpdklab
2024-07-10  5:05 ` dpdklab
2024-07-10  5:07 ` dpdklab
2024-07-10  5:13 ` |SUCCESS| " dpdklab
2024-07-10  5:14 ` |PENDING| " dpdklab
2024-07-10  5:53 ` dpdklab
2024-07-10  6:04 ` dpdklab
2024-07-10  6:25 ` |SUCCESS| " dpdklab
2024-07-10 17:21 ` |PENDING| " dpdklab
2024-07-10 17:24 ` dpdklab
2024-07-10 17:28 ` dpdklab
2024-07-10 17:32 ` dpdklab
2024-07-10 17:35 ` dpdklab
2024-07-10 17:38 ` dpdklab
2024-07-10 17:40 ` dpdklab
2024-07-10 17:42 ` dpdklab [this message]
2024-07-10 17:47 ` dpdklab
2024-07-10 17:53 ` dpdklab
2024-07-10 17:55 ` |SUCCESS| " dpdklab
2024-07-10 17:59 ` dpdklab
2024-07-10 18:40 ` |PENDING| " dpdklab
2024-07-10 18:42 ` dpdklab
2024-07-10 18:45 ` dpdklab
2024-07-10 18:47 ` dpdklab
2024-07-10 18:50 ` dpdklab
2024-07-10 18:56 ` dpdklab
2024-07-10 18:57 ` dpdklab
2024-07-10 18:58 ` dpdklab
2024-07-10 19:02 ` dpdklab
2024-07-10 19:05 ` |SUCCESS| " dpdklab
2024-07-13 13:41 ` dpdklab
2024-07-14  8:45 ` dpdklab
2024-07-14 15:22 ` dpdklab
2024-07-15  3:41 ` dpdklab
2024-07-15  3:45 ` 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=668ec813.170a0220.6fa08.797eSMTPIN_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).