From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw144367 [PATCH] [RFC] mempool: obey configured cache size
Date: Fri, 20 Sep 2024 13:32:47 -0700 (PDT) [thread overview]
Message-ID: <66eddbef.050a0220.f5430.dfffSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240920163203.840770-1-mb@smartsharesystems.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/144367
_Functional Testing PASS_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Friday, September 20 2024 16:32:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
144367 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#182704
Test environment and result as below:
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 |
+-----------------------------+--------+
Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
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/31102/
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-09-20 20:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240920163203.840770-1-mb@smartsharesystems.com>
2024-09-20 16:05 ` |SUCCESS| pw144367 [RFC PATCH] " qemudev
2024-09-20 16:09 ` qemudev
2024-09-20 16:34 ` |WARNING| " checkpatch
2024-09-20 17:05 ` |FAILURE| " 0-day Robot
2024-09-20 19:13 ` |SUCCESS| pw144367 [PATCH] [RFC] " dpdklab
2024-09-20 19:18 ` dpdklab
2024-09-20 20:11 ` dpdklab
2024-09-20 20:32 ` dpdklab [this message]
2024-09-20 21:03 ` |FAILURE| " dpdklab
2024-09-20 21:03 ` |WARNING| " dpdklab
2024-09-20 21:04 ` |FAILURE| " dpdklab
2024-09-20 21:17 ` dpdklab
2024-09-20 21:17 ` dpdklab
2024-09-20 21:24 ` |WARNING| " dpdklab
2024-09-20 22:01 ` |SUCCESS| " dpdklab
2024-09-20 22:20 ` |FAILURE| " dpdklab
2024-09-20 22:20 ` dpdklab
2024-09-20 22:20 ` dpdklab
2024-09-20 22:20 ` dpdklab
2024-09-20 22:24 ` dpdklab
2024-09-20 22:27 ` dpdklab
2024-09-20 22:27 ` dpdklab
2024-09-20 22:27 ` dpdklab
2024-09-20 22:27 ` dpdklab
2024-09-20 22:28 ` dpdklab
2024-09-20 22:29 ` dpdklab
2024-09-20 22:31 ` dpdklab
2024-09-20 22:31 ` dpdklab
2024-09-20 22:32 ` |WARNING| " dpdklab
2024-09-20 22:32 ` |FAILURE| " dpdklab
2024-09-20 22:33 ` dpdklab
2024-09-20 22:35 ` dpdklab
2024-09-20 22:36 ` dpdklab
2024-09-20 22:36 ` |SUCCESS| " dpdklab
2024-09-20 22:39 ` |FAILURE| " dpdklab
2024-09-20 22:42 ` dpdklab
2024-09-20 22:51 ` dpdklab
2024-09-20 23:06 ` dpdklab
2024-09-20 23:09 ` dpdklab
2024-09-20 23:13 ` dpdklab
2024-09-20 23:15 ` dpdklab
2024-09-20 23:16 ` dpdklab
2024-09-20 23:16 ` dpdklab
2024-09-20 23:18 ` |WARNING| " dpdklab
2024-09-20 23:18 ` dpdklab
2024-09-20 23:19 ` dpdklab
2024-09-20 23:20 ` dpdklab
2024-09-21 1:06 ` |FAILURE| " dpdklab
2024-09-21 1:56 ` dpdklab
2024-09-21 15:13 ` |WARNING| " dpdklab
2024-09-23 12:52 ` |SUCCESS| " dpdklab
2024-09-23 15:19 ` 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=66eddbef.050a0220.f5430.dfffSMTPIN_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).