From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw144412 [PATCH] [RFC,v6] mempool: fix mempool cache size
Date: Thu, 26 Sep 2024 12:09:30 -0700 (PDT) [thread overview]
Message-ID: <66f5b16a.250a0220.27d222.18a7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240924115822.1460078-1-mb@smartsharesystems.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/144412
_Testing PASS_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Tuesday, September 24 2024 11:58:22
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
144412 --> testing pass
Upstream job id: ACVP-FIPS-testing#7074
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/31124/
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-26 19:09 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240924115822.1460078-1-mb@smartsharesystems.com>
2024-09-24 11:30 ` |SUCCESS| pw144412 [RFC PATCH v6] " qemudev
2024-09-24 11:35 ` qemudev
2024-09-24 11:59 ` checkpatch
2024-09-24 13:03 ` 0-day Robot
2024-09-24 16:44 ` |SUCCESS| pw144412 [PATCH] [RFC,v6] " dpdklab
2024-09-24 16:52 ` |PENDING| " dpdklab
2024-09-24 16:58 ` |SUCCESS| " dpdklab
2024-09-24 17:01 ` dpdklab
2024-09-24 17:02 ` |FAILURE| " dpdklab
2024-09-24 17:08 ` |SUCCESS| " dpdklab
2024-09-24 17:10 ` dpdklab
2024-09-24 17:20 ` |PENDING| " dpdklab
2024-09-24 17:30 ` |SUCCESS| " dpdklab
2024-09-24 18:07 ` dpdklab
2024-09-24 18:19 ` |PENDING| " dpdklab
2024-09-24 18:29 ` |SUCCESS| " dpdklab
2024-09-24 19:02 ` dpdklab
2024-09-24 19:07 ` dpdklab
2024-09-24 20:59 ` dpdklab
2024-09-24 21:00 ` dpdklab
2024-09-26 17:21 ` |PENDING| " dpdklab
2024-09-26 17:23 ` |SUCCESS| " dpdklab
2024-09-26 17:24 ` |FAILURE| " dpdklab
2024-09-26 17:25 ` |SUCCESS| " dpdklab
2024-09-26 17:26 ` dpdklab
2024-09-26 17:31 ` dpdklab
2024-09-26 17:33 ` dpdklab
2024-09-26 17:33 ` dpdklab
2024-09-26 17:36 ` dpdklab
2024-09-26 17:41 ` dpdklab
2024-09-26 17:45 ` |PENDING| " dpdklab
2024-09-26 17:47 ` |SUCCESS| " dpdklab
2024-09-26 18:07 ` dpdklab
2024-09-26 18:38 ` |FAILURE| " dpdklab
2024-09-26 18:39 ` dpdklab
2024-09-26 19:09 ` dpdklab [this message]
2024-09-26 19:13 ` |SUCCESS| " dpdklab
2024-09-26 20:45 ` dpdklab
2024-09-26 21:46 ` 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=66f5b16a.250a0220.27d222.18a7SMTPIN_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).