From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw151795 [PATCH] [RFC,v18] mempool: fix mempool cache size
Date: Fri, 21 Feb 2025 12:17:18 -0800 (PST) [thread overview]
Message-ID: <67b8df4e.170a0220.65e37.8254SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250221151318.145254-1-mb@smartsharesystems.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/151795
_Testing PASS_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Friday, February 21 2025 15:13:18
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fab31a03ba98e7457284df95dd9eef2223a4ccaa
151795 --> testing pass
Upstream job id: Generic-Unit-Test-DPDK#317267
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| Debian Bullseye | PASS |
+-----------------+----------------+
| RHEL9 | PASS |
+-----------------+----------------+
Debian Bullseye
Kernel: Depends on container host
Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32638/
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-02-21 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250221151318.145254-1-mb@smartsharesystems.com>
2025-02-21 14:47 ` |SUCCESS| pw151795 [RFC PATCH v18] " qemudev
2025-02-21 14:51 ` qemudev
2025-02-21 15:15 ` checkpatch
2025-02-21 16:24 ` 0-day Robot
2025-02-21 19:57 ` |PENDING| pw151795 [PATCH] [RFC,v18] " dpdklab
2025-02-21 20:17 ` dpdklab [this message]
2025-02-21 20:21 ` dpdklab
2025-02-21 20:23 ` |SUCCESS| " dpdklab
2025-02-21 20:44 ` 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=67b8df4e.170a0220.65e37.8254SMTPIN_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).