From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw149604-149606 [PATCH] [v11,3/3] drivers/net: add diagnos
Date: Fri, 03 Jan 2025 14:19:12 -0800 (PST) [thread overview]
Message-ID: <67786260.050a0220.250098.05aeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1735918611-17374-4-git-send-email-andremue@linux.microsoft.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/149606
_Functional Testing PASS_
Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Friday, January 03 2025 15:36:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fd51012de5369679e807be1d6a81d63ef15015ce
149604-149606 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#205266
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/32249/
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-03 22:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1735918611-17374-4-git-send-email-andremue@linux.microsoft.com>
2025-01-03 15:19 ` |SUCCESS| pw149604-149606 [PATCH v11 3/3] drivers/net: add diagnostics macros to make code portable qemudev
2025-01-03 15:23 ` qemudev
2025-01-03 15:38 ` |WARNING| pw149606 " checkpatch
2025-01-03 16:24 ` |SUCCESS| " 0-day Robot
2025-01-03 22:01 ` |PENDING| pw149604-149606 [PATCH] [v11,3/3] drivers/net: add diagnos dpdklab
2025-01-03 22:02 ` dpdklab
2025-01-03 22:03 ` |SUCCESS| " dpdklab
2025-01-03 22:05 ` dpdklab
2025-01-03 22:08 ` dpdklab
2025-01-03 22:10 ` dpdklab
2025-01-03 22:14 ` dpdklab
2025-01-03 22:16 ` dpdklab
2025-01-03 22:17 ` dpdklab
2025-01-03 22:19 ` dpdklab [this message]
2025-01-03 22:22 ` |PENDING| " dpdklab
2025-01-03 22:23 ` dpdklab
2025-01-03 22:36 ` dpdklab
2025-01-03 22:36 ` |SUCCESS| " dpdklab
2025-01-03 22:40 ` dpdklab
2025-01-03 22:51 ` dpdklab
2025-01-03 22:56 ` dpdklab
2025-01-03 23:50 ` dpdklab
2025-01-04 0:08 ` |WARNING| " dpdklab
2025-01-04 0:41 ` |SUCCESS| " dpdklab
2025-01-04 2:42 ` 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=67786260.050a0220.250098.05aeSMTPIN_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).