From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Sunil Kumar Kori <skori@marvell.com>
Subject: |FAILURE| pw153188 [PATCH] ethdev: remove callback checks from fast
Date: Tue, 29 Apr 2025 11:45:49 -0700 (PDT) [thread overview]
Message-ID: <68111e5d.050a0220.1235c6.584cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250429181132.2544771-1-skori@marvell.com>
Test-Label: iol-mellanox-Functional
Test-Status: FAILURE
http://dpdk.org/patch/153188
_Functional Testing issues_
Submitter: Sunil Kumar Kori <skori@marvell.com>
Date: Tuesday, April 29 2025 18:11:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ff05ee3e3f8fb4ce958a2ce6461e8141aea959c6
153188 --> functional testing issues
Upstream job id: Template-DPDK-DTS-Pipeline#457
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 | FAIL |
+----------------------------------+--------+
| TestUniPkt | FAIL |
+----------------------------------+--------+
| TestDynamicConfig | FAIL |
+----------------------------------+--------+
| TestHelloWorld | FAIL |
+----------------------------------+--------+
| TestL2fwd | FAIL |
+----------------------------------+--------+
| TestMacFilter | FAIL |
+----------------------------------+--------+
| TestMTU | FAIL |
+----------------------------------+--------+
| TestPortRestartConfigPersistency | FAIL |
+----------------------------------+--------+
| TestSoftNIC | FAIL |
+----------------------------------+--------+
| TestVLAN | FAIL |
+----------------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33088/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-04-29 18:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250429181132.2544771-1-skori@marvell.com>
2025-04-29 17:37 ` |SUCCESS| pw153188 [PATCH] ethdev: remove callback checks from fast path qemudev
2025-04-29 17:41 ` qemudev
2025-04-29 18:12 ` checkpatch
2025-04-29 18:45 ` dpdklab [this message]
2025-04-29 18:48 ` |SUCCESS| pw153188 [PATCH] ethdev: remove callback checks from fast dpdklab
2025-04-29 18:59 ` |PENDING| " dpdklab
2025-04-29 19:00 ` |SUCCESS| " dpdklab
2025-04-29 19:02 ` dpdklab
2025-04-29 19:04 ` |PENDING| " dpdklab
2025-04-29 19:08 ` |SUCCESS| " dpdklab
2025-04-29 19:09 ` dpdklab
2025-04-29 19:10 ` |PENDING| " dpdklab
2025-04-29 19:13 ` dpdklab
2025-04-29 19:14 ` |SUCCESS| " dpdklab
2025-04-29 19:18 ` dpdklab
2025-04-29 19:26 ` |SUCCESS| pw153188 [PATCH] ethdev: remove callback checks from fast path 0-day Robot
2025-04-29 19:40 ` |SUCCESS| pw153188 [PATCH] ethdev: remove callback checks from fast dpdklab
2025-04-29 20:06 ` |WARNING| " dpdklab
2025-04-29 20:15 ` |SUCCESS| " dpdklab
2025-04-29 21:32 ` dpdklab
2025-04-29 21:34 ` dpdklab
2025-04-29 22:56 ` 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=68111e5d.050a0220.1235c6.584cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=skori@marvell.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).