From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw144610 [PATCH] [RFC,v12] mempool: fix mempool cache size
Date: Sat, 28 Sep 2024 13:16:43 -0700 (PDT) [thread overview]
Message-ID: <66f8642b.170a0220.3cebef.6ce5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240928193841.1993128-1-mb@smartsharesystems.com>
Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/144610
_Testing pending_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Saturday, September 28 2024 19:38:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:bf0ff8df59c7e32f95c0b542cc4a7918f8a3da84
144610 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#267380
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PEND |
+---------------------+----------------+
| CentOS Stream 9 | PEND |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian 12 | PEND |
+---------------------+----------------+
| Fedora 37 | PEND |
+---------------------+----------------+
| Fedora 38 (Clang) | PEND |
+---------------------+----------------+
| Fedora 39 (Clang) | PEND |
+---------------------+----------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)
Fedora 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31171/
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-28 20:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240928193841.1993128-1-mb@smartsharesystems.com>
2024-09-28 19:12 ` |SUCCESS| pw144610 [RFC PATCH v12] " qemudev
2024-09-28 19:17 ` qemudev
2024-09-28 19:39 ` checkpatch
2024-09-28 20:16 ` dpdklab [this message]
2024-09-28 20:19 ` |FAILURE| pw144610 [PATCH] [RFC,v12] " dpdklab
2024-09-28 20:23 ` |PENDING| " dpdklab
2024-09-28 20:24 ` dpdklab
2024-09-28 20:26 ` |SUCCESS| " dpdklab
2024-09-28 20:28 ` dpdklab
2024-09-28 20:31 ` dpdklab
2024-09-28 20:33 ` |PENDING| " dpdklab
2024-09-28 20:37 ` |SUCCESS| " dpdklab
2024-09-28 20:39 ` dpdklab
2024-09-28 20:40 ` dpdklab
2024-09-28 20:40 ` |PENDING| " dpdklab
2024-09-28 20:43 ` |SUCCESS| pw144610 [RFC PATCH v12] " 0-day Robot
2024-09-28 20:59 ` |SUCCESS| pw144610 [PATCH] [RFC,v12] " dpdklab
2024-09-28 21:04 ` |FAILURE| " dpdklab
2024-09-28 21:36 ` |SUCCESS| " dpdklab
2024-09-28 21:38 ` dpdklab
2024-09-28 21:39 ` dpdklab
2024-09-28 21:39 ` dpdklab
2024-09-28 22:58 ` dpdklab
2024-09-29 0:10 ` 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=66f8642b.170a0220.3cebef.6ce5SMTPIN_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).