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| pw155350-155362 [PATCH] [v10,14/14] net/sxe: add Solve com
Date: Sat, 19 Jul 2025 03:05:06 -0700 (PDT)	[thread overview]
Message-ID: <687b6dd2.050a0220.105f12.e9a9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250719090537.699357-14-liujie5@linkdatatechnology.com>

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

_Testing pending_

Submitter: Jie Liu <liujie5@linkdatatechnology.com>
Date: Saturday, July 19 2025 09:05:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f6e3473724e7ce31103fa0ecad62b282ec8e7090

155350-155362 --> testing pending

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

Test environment and result as below:

+------------------------------+--------------------+
|         Environment          | dpdk_meson_compile |
+==============================+====================+
| Red Hat Enterprise Linux 9.5 | PEND               |
+------------------------------+--------------------+
| Ubuntu 20.04                 | PASS               |
+------------------------------+--------------------+
| Debian GNU/Linux 12          | PEND               |
+------------------------------+--------------------+
| Fedora Linux 40              | 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

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

Fedora Linux 40
	Kernel: 5.4
	Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-07-19 10:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250719090537.699357-14-liujie5@linkdatatechnology.com>
2025-07-19  8:35 ` |SUCCESS| pw155350-155362 [PATCH v10 14/14] net/sxe: add Solve compilation problems qemudev
2025-07-19  8:40 ` qemudev
2025-07-19  9:09 ` |WARNING| pw155362 " checkpatch
2025-07-19  9:41 ` |SUCCESS| pw155350-155362 [PATCH] [v10,14/14] net/sxe: add Solve com dpdklab
2025-07-19  9:46 ` dpdklab
2025-07-19  9:49 ` |PENDING| " dpdklab
2025-07-19  9:52 ` |SUCCESS| " dpdklab
2025-07-19  9:58 ` |PENDING| " dpdklab
2025-07-19 10:00 ` |SUCCESS| " dpdklab
2025-07-19 10:03 ` dpdklab
2025-07-19 10:03 ` dpdklab
2025-07-19 10:05 ` dpdklab [this message]
2025-07-19 10:05 ` dpdklab
2025-07-19 10:24 ` |FAILURE| pw155362 [PATCH v10 14/14] net/sxe: add Solve compilation problems 0-day Robot
2025-07-19 10:35 ` |PENDING| pw155350-155362 [PATCH] [v10,14/14] net/sxe: add Solve com dpdklab
2025-07-19 10:46 ` |SUCCESS| " dpdklab
2025-07-19 10:48 ` dpdklab
2025-07-19 10:54 ` dpdklab
2025-07-19 11:14 ` dpdklab
2025-07-19 11:59 ` dpdklab
2025-07-19 13:25 ` dpdklab
2025-07-19 13:25 ` 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=687b6dd2.050a0220.105f12.e9a9SMTPIN_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).