From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw150992-151002 [PATCH] [11/11] net/bnxt: address coverity
Date: Wed, 05 Feb 2025 12:25:25 -0800 (PST) [thread overview]
Message-ID: <67a3c935.050a0220.1f7ce0.72c4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250205172004.50395-12-ajit.khaparde@broadcom.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/151002
_Functional Testing PASS_
Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Wednesday, February 05 2025 17:20:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:32c18e7364e30a8e43cc7cc6709a7ce606fa285e
150992-151002 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#210880
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| cmdline | PASS |
+-----------------+--------+
| ipv4_reassembly | PASS |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32502/
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-02-05 20:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250205172004.50395-12-ajit.khaparde@broadcom.com>
2025-02-05 16:54 ` |SUCCESS| pw150992-151002 [PATCH 11/11] net/bnxt: address coverity control flow issues qemudev
2025-02-05 16:58 ` qemudev
2025-02-05 17:20 ` |SUCCESS| pw151002 " checkpatch
2025-02-05 19:25 ` 0-day Robot
2025-02-05 20:25 ` dpdklab [this message]
2025-02-05 20:32 ` |SUCCESS| pw150992-151002 [PATCH] [11/11] net/bnxt: address coverity dpdklab
2025-02-05 20:34 ` dpdklab
2025-02-05 20:45 ` |PENDING| " dpdklab
2025-02-05 20:47 ` |SUCCESS| " dpdklab
2025-02-05 20:49 ` dpdklab
2025-02-05 20:56 ` dpdklab
2025-02-05 21:00 ` dpdklab
2025-02-05 21:10 ` |PENDING| " dpdklab
2025-02-05 21:11 ` |SUCCESS| " dpdklab
2025-02-05 21:23 ` dpdklab
2025-02-05 21:29 ` |PENDING| " dpdklab
2025-02-05 21:33 ` |SUCCESS| " dpdklab
2025-02-05 21:52 ` dpdklab
2025-02-05 22:01 ` dpdklab
2025-02-05 22:07 ` |PENDING| " dpdklab
2025-02-05 22:21 ` dpdklab
2025-02-05 22:32 ` |SUCCESS| " dpdklab
2025-02-05 22:35 ` dpdklab
2025-02-05 22:53 ` |PENDING| " dpdklab
2025-02-05 23:17 ` |SUCCESS| " dpdklab
2025-02-05 23:24 ` dpdklab
2025-02-05 23:40 ` 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=67a3c935.050a0220.1f7ce0.72c4SMTPIN_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).