From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw154724-154738 [PATCH] [v3,15/15] doc: update for txgbe
Date: Thu, 26 Jun 2025 03:52:33 -0700 (PDT) [thread overview]
Message-ID: <685d2671.170a0220.35ba73.5e7cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250626080221.22488-16-zaiyuwang@trustnetic.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/154738
_Functional Testing PASS_
Submitter: Zaiyu Wang <zaiyuwang@trustnetic.com>
Date: Thursday, June 26 2025 08:02:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:62a35bbb247e608e235a04ff2941488bc1a78941
154724-154738 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#233270
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Intel Corporation QAT 8970 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/33507/
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-06-26 10:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250626080221.22488-16-zaiyuwang@trustnetic.com>
2025-06-26 7:43 ` |SUCCESS| pw154724-154738 [PATCH v3 15/15] " qemudev
2025-06-26 7:48 ` qemudev
2025-06-26 8:10 ` |WARNING| pw154738 " checkpatch
2025-06-26 9:24 ` |SUCCESS| " 0-day Robot
2025-06-26 9:29 ` |SUCCESS| pw154724-154738 [PATCH] [v3,15/15] " dpdklab
2025-06-26 9:37 ` dpdklab
2025-06-26 9:42 ` dpdklab
2025-06-26 9:52 ` dpdklab
2025-06-26 10:00 ` dpdklab
2025-06-26 10:00 ` dpdklab
2025-06-26 10:09 ` dpdklab
2025-06-26 10:09 ` dpdklab
2025-06-26 10:26 ` dpdklab
2025-06-26 10:38 ` dpdklab
2025-06-26 10:52 ` dpdklab [this message]
2025-06-26 11:09 ` dpdklab
2025-06-26 11:10 ` dpdklab
2025-06-26 11:10 ` dpdklab
2025-06-26 11:10 ` dpdklab
2025-06-26 11:11 ` |PENDING| " dpdklab
2025-06-26 11:11 ` |SUCCESS| " dpdklab
2025-06-26 11:13 ` dpdklab
2025-06-26 11:16 ` |PENDING| " dpdklab
2025-06-26 11:21 ` dpdklab
2025-06-26 11:41 ` dpdklab
2025-06-26 11:54 ` |FAILURE| " dpdklab
2025-06-26 11:55 ` dpdklab
2025-06-26 12:06 ` |PENDING| " dpdklab
2025-06-26 12:25 ` dpdklab
2025-06-26 12:32 ` dpdklab
2025-06-26 12:38 ` |FAILURE| " dpdklab
2025-06-26 12:38 ` dpdklab
2025-06-26 12:59 ` dpdklab
2025-06-26 13:01 ` |SUCCESS| " dpdklab
2025-06-26 13:11 ` |FAILURE| " dpdklab
2025-06-26 13:20 ` dpdklab
2025-06-26 13:23 ` |SUCCESS| " dpdklab
2025-06-26 13:41 ` |FAILURE| " dpdklab
2025-06-26 15:04 ` |SUCCESS| " dpdklab
2025-06-26 15:07 ` dpdklab
2025-06-26 15:31 ` |FAILURE| " dpdklab
2025-06-26 16:14 ` |SUCCESS| " 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=685d2671.170a0220.35ba73.5e7cSMTPIN_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).