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| pw152018 [PATCH] net/mlx5: fix queue counter error check
Date: Tue, 25 Feb 2025 08:10:55 -0800 (PST)	[thread overview]
Message-ID: <67bdeb8f.050a0220.32b7b4.18deSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250225090845.136968-1-dsosnowski@nvidia.com>

Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/152018

_Testing pending_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Tuesday, February 25 2025 09:08:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:61fc05f1c6a079c0b25b27d1668450134a784d56

152018 --> testing pending

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

Test environment and result as below:

+-------------------+--------------------+-------------------+------------------+
|    Environment    | dpdk_meson_compile | dpdk_compile_spdk | dpdk_compile_ovs |
+===================+====================+===================+==================+
| CentOS Stream 9   | PEND               | PEND              | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| CentOS Stream 10  | PASS               | SKIPPED           | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| Debian Bullseye   | PEND               | PEND              | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| Debian 12         | PEND               | PEND              | SKIPPED          |
+-------------------+--------------------+-------------------+------------------+
| Fedora 41 (Clang) | PEND               | PEND              | PEND             |
+-------------------+--------------------+-------------------+------------------+


CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

CentOS Stream 10
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)

Debian Bullseye
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 41 (Clang)
	Kernel: Depends on container host
	Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-02-25 16:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250225090845.136968-1-dsosnowski@nvidia.com>
2025-02-25  8:42 ` |SUCCESS| " qemudev
2025-02-25  8:46 ` qemudev
2025-02-25  9:09 ` checkpatch
2025-02-25 10:04 ` 0-day Robot
2025-02-25 15:49 ` |PENDING| " dpdklab
2025-02-25 16:00 ` dpdklab
2025-02-25 16:10 ` dpdklab [this message]
2025-02-25 16:49 ` |SUCCESS| " dpdklab
2025-02-25 16:50 ` dpdklab
2025-02-25 16:50 ` dpdklab
2025-02-25 16:51 ` dpdklab
2025-02-25 17:21 ` dpdklab
2025-02-25 17:43 ` dpdklab
2025-02-25 19:23 ` 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=67bdeb8f.050a0220.32b7b4.18deSMTPIN_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).