From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw151574 [PATCH] config/arm: update NVIDIA BlueField-3 con
Date: Tue, 18 Feb 2025 08:14:59 -0800 (PST) [thread overview]
Message-ID: <67b4b203.050a0220.2a92b1.d97cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250218104942.81984-1-getelson@nvidia.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/151574
_Functional Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, February 18 2025 10:49:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5176f23ae8b31437c3e5eb875c81f95bf3a9942
151574 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#213099
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 |
+-----------------+--------+
| dynamic_queue | PASS |
+-----------------+--------+
| ipv4_reassembly | PASS |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32600/
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-18 16:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250218104942.81984-1-getelson@nvidia.com>
2025-02-18 10:15 ` |SUCCESS| pw151574 [PATCH] config/arm: update NVIDIA BlueField-3 configuration qemudev
2025-02-18 10:19 ` qemudev
2025-02-18 10:50 ` checkpatch
2025-02-18 13:43 ` 0-day Robot
2025-02-18 15:08 ` |SUCCESS| pw151574 [PATCH] config/arm: update NVIDIA BlueField-3 con dpdklab
2025-02-18 15:10 ` dpdklab
2025-02-18 15:14 ` dpdklab
2025-02-18 15:35 ` dpdklab
2025-02-18 15:44 ` |PENDING| " dpdklab
2025-02-18 15:55 ` dpdklab
2025-02-18 15:57 ` dpdklab
2025-02-18 16:06 ` dpdklab
2025-02-18 16:14 ` dpdklab [this message]
2025-02-18 16:39 ` |SUCCESS| " dpdklab
2025-02-18 16:53 ` dpdklab
2025-02-18 16:59 ` dpdklab
2025-02-18 17:00 ` dpdklab
2025-02-18 17:02 ` dpdklab
2025-02-18 17:34 ` dpdklab
2025-02-19 9:33 ` dpdklab
2025-02-20 21:21 ` |PENDING| " dpdklab
2025-02-20 23:02 ` |SUCCESS| " dpdklab
2025-02-21 0:58 ` dpdklab
2025-02-21 9:56 ` dpdklab
2025-02-21 11:00 ` 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=67b4b203.050a0220.2a92b1.d97cSMTPIN_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).