From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw156206 [PATCH] [v2] pcapng: allow any protocol link type
Date: Wed, 27 Aug 2025 17:18:05 -0700 (PDT) [thread overview]
Message-ID: <68afa03d.170a0220.2066ff.cdb0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250827223216.1337749-1-schneide@qti.qualcomm.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/156206
_Functional Testing PASS_
Submitter: Schneide <schneide@qti.qualcomm.com>
Date: Wednesday, August 27 2025 22:32:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:38543d33bd47fc0ee21f59db80a8763620741879
156206 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#241900
Test environment and result as below:
Ubuntu 24.04 LTS
Kernel: 6.8.0-44-generic
Compiler: gcc 13.2.0
NIC: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ 40 Mbps
Aggregate Results by Test Suite
+--------------------+--------+
| Test Suite | Result |
+====================+========+
| blocklist | PASS |
+--------------------+--------+
| promisc_support | PASS |
+--------------------+--------+
| uni_pkt | PASS |
+--------------------+--------+
| dynamic_config | PASS |
+--------------------+--------+
| dynamic_queue_conf | PASS |
+--------------------+--------+
| hello_world | PASS |
+--------------------+--------+
| l2fwd | PASS |
+--------------------+--------+
| softnic | PASS |
+--------------------+--------+
| vlan | PASS |
+--------------------+--------+
Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel Corporation 4xxx Series QAT 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33971/
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-08-28 0:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250827223216.1337749-1-schneide@qti.qualcomm.com>
2025-08-27 22:05 ` |SUCCESS| pw156206 [PATCH v2] pcapng: allow any protocol link type for the interface block qemudev
2025-08-27 22:10 ` qemudev
2025-08-27 22:31 ` checkpatch
2025-08-27 22:57 ` |PENDING| pw156206 [PATCH] [v2] pcapng: allow any protocol link type dpdklab
2025-08-27 23:02 ` |SUCCESS| " dpdklab
2025-08-27 23:05 ` dpdklab
2025-08-27 23:08 ` dpdklab
2025-08-27 23:53 ` dpdklab
2025-08-28 0:04 ` |SUCCESS| pw156206 [PATCH v2] pcapng: allow any protocol link type for the interface block 0-day Robot
2025-08-28 0:10 ` |SUCCESS| pw156206 [PATCH] [v2] pcapng: allow any protocol link type dpdklab
2025-08-28 0:18 ` dpdklab [this message]
2025-08-28 0:28 ` dpdklab
2025-08-28 0:40 ` |PENDING| " dpdklab
2025-08-28 0:58 ` dpdklab
2025-08-28 1:08 ` |SUCCESS| " dpdklab
2025-08-28 1:33 ` dpdklab
2025-08-28 2:38 ` dpdklab
2025-08-28 2:53 ` |WARNING| " dpdklab
2025-08-28 2:53 ` dpdklab
2025-08-28 3:10 ` |SUCCESS| " dpdklab
2025-08-28 3:20 ` dpdklab
2025-08-28 3:36 ` |WARNING| " dpdklab
2025-08-28 3:39 ` |SUCCESS| " dpdklab
2025-08-28 4:16 ` dpdklab
2025-08-28 8:35 ` dpdklab
2025-08-28 8:48 ` 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=68afa03d.170a0220.2066ff.cdb0SMTPIN_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).