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, Gregory Etelson <getelson@nvidia.com>
Subject: |FAILURE| pw153229 [PATCH] net/mlx5: fix support for meter flow acti
Date: Sun, 04 May 2025 11:59:54 -0700 (PDT)	[thread overview]
Message-ID: <6817b92a.050a0220.64513.e8ffSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250504052350.91160-1-getelson@nvidia.com>

Test-Label: iol-mellanox-Functional
Test-Status: FAILURE
http://dpdk.org/patch/153229

_Functional Testing issues_

Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Sunday, May 04 2025 05:23:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:edd3f4b1265e6da707c46ca9b6c39d332647baea

153229 --> functional testing issues

Upstream job id: Template-DPDK-DTS-Pipeline#509

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8.0-55-generic
Compiler: gcc 13.3.0
NIC: Mellanox ConnectX-5 100000 Mbps

Aggregate Results by Test Suite
+----------------------------------+--------+
|            Test Suite            | Result |
+==================================+========+
| TestBlocklist                    |  PASS  |
+----------------------------------+--------+
| TestPMDBufferScatter             |  FAIL  |
+----------------------------------+--------+
| TestPromiscSupport               |  PASS  |
+----------------------------------+--------+
| TestUniPkt                       |  PASS  |
+----------------------------------+--------+
| TestDynamicConfig                |  FAIL  |
+----------------------------------+--------+
| TestHelloWorld                   |  PASS  |
+----------------------------------+--------+
| TestL2fwd                        |  FAIL  |
+----------------------------------+--------+
| TestMacFilter                    |  FAIL  |
+----------------------------------+--------+
| TestMTU                          |  PASS  |
+----------------------------------+--------+
| TestPortRestartConfigPersistency |  PASS  |
+----------------------------------+--------+
| TestSoftNIC                      |  FAIL  |
+----------------------------------+--------+
| TestVLAN                         |  FAIL  |
+----------------------------------+--------+


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

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2025-05-04 18:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250504052350.91160-1-getelson@nvidia.com>
2025-05-04  4:59 ` |SUCCESS| pw153229 [PATCH] net/mlx5: fix support for meter flow action in HWS qemudev
2025-05-04  5:03 ` qemudev
2025-05-04  5:26 ` checkpatch
2025-05-04  6:13 ` |SUCCESS| pw153229 [PATCH] net/mlx5: fix support for meter flow acti dpdklab
2025-05-04  6:20 ` dpdklab
2025-05-04  6:22 ` |PENDING| " dpdklab
2025-05-04  6:23 ` |SUCCESS| " dpdklab
2025-05-04  6:27 ` dpdklab
2025-05-04  6:32 ` dpdklab
2025-05-04  6:35 ` dpdklab
2025-05-04  6:36 ` dpdklab
2025-05-04  6:41 ` dpdklab
2025-05-04  6:44 ` |SUCCESS| pw153229 [PATCH] net/mlx5: fix support for meter flow action in HWS 0-day Robot
2025-05-04  6:45 ` |SUCCESS| pw153229 [PATCH] net/mlx5: fix support for meter flow acti dpdklab
2025-05-04  6:56 ` dpdklab
2025-05-04  7:09 ` dpdklab
2025-05-04  7:10 ` |PENDING| " dpdklab
2025-05-04  7:20 ` |SUCCESS| " dpdklab
2025-05-04  7:28 ` |PENDING| " dpdklab
2025-05-04  8:05 ` |SUCCESS| " dpdklab
2025-05-04  9:10 ` |PENDING| " dpdklab
2025-05-04  9:50 ` |SUCCESS| " dpdklab
2025-05-04 10:16 ` dpdklab
2025-05-04 10:21 ` dpdklab
2025-05-04 10:21 ` dpdklab
2025-05-04 12:22 ` dpdklab
2025-05-04 12:22 ` dpdklab
2025-05-04 13:38 ` dpdklab
2025-05-04 18:59 ` dpdklab [this message]

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=6817b92a.050a0220.64513.e8ffSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=getelson@nvidia.com \
    --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).