From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw150153-150154 [PATCH] [2/2] net/af_xdp: Refactor af_xdp_
Date: Thu, 16 Jan 2025 12:56:11 -0800 (PST) [thread overview]
Message-ID: <6789726b.630a0220.136ed7.318fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250116195640.68885-3-ariel.otilibili@6wind.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/150154
_Functional Testing PASS_
Submitter: Ariel Otilibili <ariel.otilibili@6wind.com>
Date: Thursday, January 16 2025 19:56:39
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:34ea86164bf17a431ec5ef78d7e51e2e9b3fd75e
150153-150154 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#207377
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/32350/
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-01-16 20:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250116195640.68885-3-ariel.otilibili@6wind.com>
2025-01-16 19:27 ` |SUCCESS| pw150153-150154 [PATCH 2/2] net/af_xdp: Refactor af_xdp_tx_zc() qemudev
2025-01-16 19:31 ` qemudev
2025-01-16 19:57 ` |SUCCESS| pw150154 [PATCH 2/2] net/af_xdp: Refactor af_xdp_tx_zc checkpatch
2025-01-16 20:31 ` |FAILURE| pw150153-150154 [PATCH] [2/2] net/af_xdp: Refactor af_xdp_ dpdklab
2025-01-16 20:36 ` |WARNING| " dpdklab
2025-01-16 20:36 ` dpdklab
2025-01-16 20:40 ` |FAILURE| " dpdklab
2025-01-16 20:41 ` dpdklab
2025-01-16 20:42 ` |SUCCESS| " dpdklab
2025-01-16 20:44 ` |FAILURE| pw150154 [PATCH 2/2] net/af_xdp: Refactor af_xdp_tx_zc() 0-day Robot
2025-01-16 20:46 ` |WARNING| pw150153-150154 [PATCH] [2/2] net/af_xdp: Refactor af_xdp_ dpdklab
2025-01-16 20:48 ` |SUCCESS| " dpdklab
2025-01-16 20:50 ` dpdklab
2025-01-16 20:52 ` dpdklab
2025-01-16 20:54 ` dpdklab
2025-01-16 20:55 ` |PENDING| " dpdklab
2025-01-16 20:56 ` dpdklab [this message]
2025-01-16 20:58 ` |FAILURE| " dpdklab
2025-01-16 21:01 ` |WARNING| " dpdklab
2025-01-16 21:03 ` |FAILURE| " dpdklab
2025-01-16 21:05 ` |SUCCESS| " dpdklab
2025-01-16 21:17 ` |WARNING| " dpdklab
2025-01-16 21:18 ` dpdklab
2025-01-16 21:25 ` dpdklab
2025-01-16 21:28 ` |SUCCESS| " dpdklab
2025-01-16 21:35 ` |WARNING| " dpdklab
2025-01-16 21:49 ` |FAILURE| " dpdklab
2025-01-16 22:39 ` |WARNING| " dpdklab
2025-01-17 0:25 ` |FAILURE| " 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=6789726b.630a0220.136ed7.318fSMTPIN_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).