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| pw156053-156055 [PATCH] [RFC,3/3] hash: add support for co
Date: Fri, 22 Aug 2025 04:45:25 -0700 (PDT)	[thread overview]
Message-ID: <68a85855.050a0220.1445e7.4bb0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250821203646.133506-4-stephen@networkplumber.org>

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

_Testing pending_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, August 21 2025 20:35:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:38543d33bd47fc0ee21f59db80a8763620741879

156053-156055 --> testing pending

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

Test environment and result as below:

+---------------------+--------------------+
|     Environment     | dpdk_meson_compile |
+=====================+====================+
| Fedora Linux 42     | PEND               |
+---------------------+--------------------+
| Ubuntu 20.04        | PASS               |
+---------------------+--------------------+
| Ubuntu 22.04        | PEND               |
+---------------------+--------------------+
| Debian GNU/Linux 12 | PEND               |
+---------------------+--------------------+


Fedora Linux 42
	Kernel: 5.4
	Compiler: clang gcc (GCC) 15.1.1 20250521 (Red Hat 15.1.1-2)

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

Ubuntu 22.04
	Kernel: 5.4
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Debian GNU/Linux 12
	Kernel: 5.4
	Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-08-22 11:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250821203646.133506-4-stephen@networkplumber.org>
2025-08-21 20:11 ` |SUCCESS| pw156053-156055 [RFC 3/3] hash: add support for common small key sizes qemudev
2025-08-21 20:16 ` qemudev
2025-08-21 20:35 ` |SUCCESS| pw156055 " checkpatch
2025-08-21 21:34 ` |SUCCESS| pw156053-156055 [PATCH] [RFC,3/3] hash: add support for co dpdklab
2025-08-21 21:44 ` |SUCCESS| pw156055 [RFC 3/3] hash: add support for common small key sizes 0-day Robot
2025-08-21 21:54 ` |SUCCESS| pw156053-156055 [PATCH] [RFC,3/3] hash: add support for co dpdklab
2025-08-21 21:59 ` dpdklab
2025-08-21 21:59 ` dpdklab
2025-08-21 22:06 ` dpdklab
2025-08-21 22:07 ` |PENDING| " dpdklab
2025-08-21 22:11 ` dpdklab
2025-08-21 22:11 ` |SUCCESS| " dpdklab
2025-08-21 22:19 ` dpdklab
2025-08-21 22:31 ` dpdklab
2025-08-21 22:34 ` dpdklab
2025-08-21 22:38 ` dpdklab
2025-08-21 22:39 ` dpdklab
2025-08-21 22:48 ` dpdklab
2025-08-21 23:07 ` dpdklab
2025-08-21 23:26 ` dpdklab
2025-08-21 23:31 ` dpdklab
2025-08-21 23:35 ` dpdklab
2025-08-22  6:51 ` dpdklab
2025-08-22 11:45 ` dpdklab [this message]
2025-08-22 15:11 ` dpdklab
2025-08-22 19:53 ` 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=68a85855.050a0220.1445e7.4bb0SMTPIN_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).