From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Morten Brorup <mb@smartsharesystems.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136100 [PATCH] [v5] mempool: test performance with large
Date: Wed, 24 Jan 2024 05:47:22 -0800 (PST) [thread overview]
Message-ID: <65b114ea.050a0220.45335.f38eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136100
_Testing PASS_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Wednesday, January 24 2024 11:21:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0c4a63ce783f55df6b43e519201474c56b5cce36
136100 --> testing pass
Test environment and result as below:
+--------------------------+----------------+---------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_zuc_autotest |
+==========================+================+===========================+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Fedora 38 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Ubuntu 20.04 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Debian 11 (arm) | SKIPPED | PASS |
+--------------------------+----------------+---------------------------+
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28948/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-24 13:47 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 13:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-24 17:23 dpdklab
2024-01-24 16:38 dpdklab
2024-01-24 16:28 dpdklab
2024-01-24 15:47 dpdklab
2024-01-24 14:39 dpdklab
2024-01-24 14:36 dpdklab
2024-01-24 14:13 dpdklab
2024-01-24 14:00 dpdklab
2024-01-24 13:59 dpdklab
2024-01-24 13:53 dpdklab
2024-01-24 13:53 dpdklab
2024-01-24 13:49 dpdklab
2024-01-24 13:48 dpdklab
2024-01-24 13:48 dpdklab
2024-01-24 13:48 dpdklab
2024-01-24 13:48 dpdklab
2024-01-24 13:47 dpdklab
2024-01-24 13:47 dpdklab
2024-01-24 13:47 dpdklab
2024-01-24 13:47 dpdklab
2024-01-24 13:46 dpdklab
2024-01-24 13:46 dpdklab
2024-01-24 13:46 dpdklab
2024-01-24 13:46 dpdklab
2024-01-24 13:46 dpdklab
2024-01-24 13:45 dpdklab
2024-01-24 13:45 dpdklab
2024-01-24 13:45 dpdklab
2024-01-24 13:44 dpdklab
2024-01-24 13:44 dpdklab
2024-01-24 13:44 dpdklab
2024-01-24 13:43 dpdklab
2024-01-24 13:43 dpdklab
2024-01-24 13:43 dpdklab
2024-01-24 13:42 dpdklab
2024-01-24 13:42 dpdklab
2024-01-24 13:42 dpdklab
2024-01-24 13:41 dpdklab
2024-01-24 13:41 dpdklab
2024-01-24 13:41 dpdklab
2024-01-24 13:41 dpdklab
2024-01-24 13:40 dpdklab
2024-01-24 13:38 dpdklab
2024-01-24 13:38 dpdklab
2024-01-24 13:38 dpdklab
2024-01-24 13:36 dpdklab
2024-01-24 13:34 dpdklab
2024-01-24 13:31 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=65b114ea.050a0220.45335.f38eSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=mb@smartsharesystems.com \
--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).