From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw149049 [PATCH] net/ice/base: support switch recipe reuse
Date: Fri, 06 Dec 2024 01:51:44 -0800 (PST) [thread overview]
Message-ID: <6752c930.170a0220.39d5b2.e265SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241206013825.2101540-1-zhichaox.zeng@intel.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/149049
_Testing PASS_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Friday, December 06 2024 01:38:25
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ce85dd8562ad9673eb4fe46b4a8bd3a508e8b32f
149049 --> testing pass
Upstream job id: Template-DTS-Pipeline#201392
Test environment and result as below:
+--------------------+----------------------+----------------------+
| Environment | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04 | SKIPPED | PASS |
+--------------------+----------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32096/
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:[~2024-12-06 9:51 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241206013825.2101540-1-zhichaox.zeng@intel.com>
2024-12-06 1:08 ` qemudev
2024-12-06 1:13 ` qemudev
2024-12-06 1:24 ` checkpatch
2024-12-06 2:42 ` 0-day Robot
2024-12-06 7:46 ` dpdklab
2024-12-06 7:53 ` |PENDING| " dpdklab
2024-12-06 7:57 ` |SUCCESS| " dpdklab
2024-12-06 8:05 ` dpdklab
2024-12-06 8:09 ` |PENDING| " dpdklab
2024-12-06 8:09 ` |SUCCESS| " dpdklab
2024-12-06 8:11 ` |PENDING| " dpdklab
2024-12-06 8:13 ` dpdklab
2024-12-06 8:23 ` |SUCCESS| " dpdklab
2024-12-06 8:27 ` dpdklab
2024-12-06 8:34 ` dpdklab
2024-12-06 8:36 ` dpdklab
2024-12-06 8:40 ` dpdklab
2024-12-06 8:51 ` |PENDING| " dpdklab
2024-12-06 8:52 ` |SUCCESS| " dpdklab
2024-12-06 9:00 ` dpdklab
2024-12-06 9:25 ` dpdklab
2024-12-06 9:25 ` dpdklab
2024-12-06 9:30 ` dpdklab
2024-12-06 9:46 ` dpdklab
2024-12-06 9:47 ` dpdklab
2024-12-06 9:51 ` dpdklab [this message]
2024-12-06 9:52 ` dpdklab
2024-12-06 9:59 ` dpdklab
2024-12-06 10:07 ` dpdklab
2024-12-06 10:37 ` dpdklab
2024-12-06 10:37 ` dpdklab
2024-12-06 10:38 ` dpdklab
2024-12-06 10:41 ` dpdklab
2024-12-06 11:06 ` dpdklab
2024-12-06 11:13 ` dpdklab
2024-12-06 11:17 ` dpdklab
2024-12-06 11:36 ` dpdklab
2024-12-07 0:02 ` |PENDING| " dpdklab
2024-12-07 0:24 ` dpdklab
2024-12-07 2:05 ` |WARNING| " dpdklab
2024-12-07 2:24 ` dpdklab
2024-12-07 3:09 ` dpdklab
2024-12-07 3:30 ` dpdklab
2024-12-07 3:34 ` dpdklab
2024-12-07 4:03 ` dpdklab
2024-12-07 4:07 ` 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=6752c930.170a0220.39d5b2.e265SMTPIN_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).