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| pw158077 [PATCH] [v6,1/1] eal/riscv: optimize rte_memcpy w
Date: Fri, 24 Oct 2025 18:55:40 -0700 (PDT)	[thread overview]
Message-ID: <68fc2e1c.d40a0220.30f413.3c03SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251024072734.1573077-2-chen.qiguo@zte.com.cn>

Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/158077

_Testing pending_

Submitter: Qiguo Chen <chen.qiguo@zte.com.cn>
Date: Friday, October 24 2025 07:27:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6edcec237e31fcdb848cca6c151ee7a5bf057c28

158077 --> testing pending

Upstream job id: Generic-DPDK-Compile-Meson#437451

Test environment and result as below:

+------------------------------+--------------------+
|         Environment          | dpdk_meson_compile |
+==============================+====================+
| Red Hat Enterprise Linux 9.5 | PEND               |
+------------------------------+--------------------+
| Ubuntu 20.04                 | PEND               |
+------------------------------+--------------------+


Red Hat Enterprise Linux 9.5
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)

Ubuntu 20.04
	Kernel: 5.15
	Compiler: aarch64-linux-gnu-gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-10-25  1:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251024072734.1573077-2-chen.qiguo@zte.com.cn>
2025-10-24  7:17 ` |SUCCESS| pw158077 [PATCH v6 1/1] eal/riscv: optimize rte_memcpy with vector and zicbop extensions qemudev
2025-10-24  7:22 ` qemudev
2025-10-24  7:44 ` checkpatch
2025-10-24  8:09 ` |PENDING| pw158077 [PATCH] [v6,1/1] eal/riscv: optimize rte_memcpy w dpdklab
2025-10-24  8:12 ` dpdklab
2025-10-24  8:13 ` |SUCCESS| " dpdklab
2025-10-24  8:17 ` dpdklab
2025-10-24  8:20 ` |WARNING| " dpdklab
2025-10-24  8:21 ` dpdklab
2025-10-24  8:29 ` |SUCCESS| " dpdklab
2025-10-24  8:32 ` dpdklab
2025-10-24  8:34 ` dpdklab
2025-10-24  8:34 ` dpdklab
2025-10-24  8:35 ` dpdklab
2025-10-24  8:38 ` |PENDING| " dpdklab
2025-10-24  8:40 ` |SUCCESS| " dpdklab
2025-10-24  8:44 ` |SUCCESS| pw158077 [PATCH v6 1/1] eal/riscv: optimize rte_memcpy with vector and zicbop extensions 0-day Robot
2025-10-24  8:44 ` 0-day Robot
2025-10-24  9:02 ` |SUCCESS| pw158077 [PATCH] [v6,1/1] eal/riscv: optimize rte_memcpy w dpdklab
2025-10-24  9:06 ` |WARNING| " dpdklab
2025-10-24  9:12 ` |SUCCESS| " dpdklab
2025-10-25  1:55 ` dpdklab [this message]
2025-10-25  8:05 ` |WARNING| " dpdklab
2025-10-25  8:34 ` dpdklab
2025-10-25 18:15 ` |SUCCESS| " dpdklab
2025-10-25 18:16 ` 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=68fc2e1c.d40a0220.30f413.3c03SMTPIN_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).