From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw152479-152489 [PATCH] [v4,11/11] member: use common AVX5
Date: Wed, 19 Mar 2025 13:34:35 -0700 (PDT) [thread overview]
Message-ID: <67db2a5b.050a0220.2a800e.9834SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250319172942.2992053-12-bruce.richardson@intel.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152489
_Functional Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wednesday, March 19 2025 17:29:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7246d0a80cb79a04e1334393ef507aa4ef7accd9
152479-152489 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#218268
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 |
+======================+========+
| TestBlocklist | PASS |
+----------------------+--------+
| TestMacFilter | PASS |
+----------------------+--------+
| TestDynamicConfig | PASS |
+----------------------+--------+
| TestDynamicQueueConf | PASS |
+----------------------+--------+
| TestPMDBufferScatter | PASS |
+----------------------+--------+
| TestPromiscSupport | PASS |
+----------------------+--------+
| TestUniPkt | PASS |
+----------------------+--------+
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32849/
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-03-19 20:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250319172942.2992053-12-bruce.richardson@intel.com>
2025-03-19 16:57 ` |SUCCESS| pw152479-152489 [PATCH v4 11/11] member: use common AVX512 build support qemudev
2025-03-19 17:02 ` qemudev
2025-03-19 17:32 ` |SUCCESS| pw152489 " checkpatch
2025-03-19 18:23 ` |FAILURE| " 0-day Robot
2025-03-19 20:16 ` |SUCCESS| pw152479-152489 [PATCH] [v4,11/11] member: use common AVX5 dpdklab
2025-03-19 20:21 ` dpdklab
2025-03-19 20:28 ` dpdklab
2025-03-19 20:29 ` dpdklab
2025-03-19 20:31 ` dpdklab
2025-03-19 20:34 ` dpdklab [this message]
2025-03-19 20:38 ` |PENDING| " dpdklab
2025-03-19 20:45 ` |SUCCESS| " dpdklab
2025-03-19 20:55 ` dpdklab
2025-03-19 20:57 ` dpdklab
2025-03-19 21:14 ` |FAILURE| " dpdklab
2025-03-19 21:22 ` |PENDING| " dpdklab
2025-03-19 21:44 ` |SUCCESS| " dpdklab
2025-03-19 21:48 ` dpdklab
2025-03-19 22:06 ` |FAILURE| " dpdklab
2025-03-19 22:10 ` |SUCCESS| " dpdklab
2025-03-19 22:12 ` dpdklab
2025-03-19 22:26 ` dpdklab
2025-03-19 23:13 ` 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=67db2a5b.050a0220.2a800e.9834SMTPIN_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).