automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw155202 [PATCH] [RFC] doc: clarify VLAN and QinQ strippin
Date: Mon, 14 Jul 2025 07:15:29 -0700 (PDT)	[thread overview]
Message-ID: <68751101.050a0220.1ab3b.191eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250714133014.44597-1-bruce.richardson@intel.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/155202

_Functional Testing PASS_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Monday, July 14 2025 13:30:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9fe9c0b231c8da5435bfccb1963121b4277f961c

155202 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#236655

Test environment and result as below:

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/33649/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2025-07-14 14:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250714133014.44597-1-bruce.richardson@intel.com>
2025-07-14 12:55 ` |SUCCESS| pw155202 [RFC PATCH] doc: clarify VLAN and QinQ stripping behaviour qemudev
2025-07-14 13:00 ` qemudev
2025-07-14 13:29 ` checkpatch
2025-07-14 14:15 ` dpdklab [this message]
2025-07-14 14:25 ` |PENDING| pw155202 [PATCH] [RFC] doc: clarify VLAN and QinQ strippin dpdklab
2025-07-14 14:42 ` |SUCCESS| " dpdklab
2025-07-14 14:42 ` |PENDING| " dpdklab
2025-07-14 14:43 ` |SUCCESS| " dpdklab
2025-07-14 14:43 ` |PENDING| " dpdklab
2025-07-14 15:48 ` |SUCCESS| " dpdklab
2025-07-14 15:49 ` dpdklab
2025-07-14 15:49 ` dpdklab
2025-07-14 15:49 ` dpdklab
2025-07-14 15:50 ` dpdklab
2025-07-14 15:50 ` dpdklab
2025-07-14 15:50 ` dpdklab
2025-07-14 15:52 ` dpdklab
2025-07-14 16:21 ` dpdklab
2025-07-14 16:21 ` dpdklab
2025-07-14 19:09 ` dpdklab
2025-07-14 20:21 ` dpdklab
2025-07-14 21:32 ` dpdklab
2025-07-14 21:35 ` 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=68751101.050a0220.1ab3b.191eSMTPIN_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).