From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133168-133169 [PATCH] [v2,2/2] mempool: clarify enqueue
Date: Mon, 23 Oct 2023 06:38:07 -0700 (PDT) [thread overview]
Message-ID: <6536773f.630a0220.d98ff.59a1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133169
_Testing PASS_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Monday, October 23 2023 09:38:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2cd2cf0cc53a508c4bd951a980ec534a646260de
133168-133169 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| Debian Buster | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| Fedora 37 | PASS |
+-----------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28037/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-23 13:38 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 13:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-23 16:37 dpdklab
2023-10-23 15:18 dpdklab
2023-10-23 14:50 dpdklab
2023-10-23 14:48 dpdklab
2023-10-23 14:33 dpdklab
2023-10-23 14:33 dpdklab
2023-10-23 14:21 dpdklab
2023-10-23 14:20 dpdklab
2023-10-23 14:06 dpdklab
2023-10-23 14:02 dpdklab
2023-10-23 14:01 dpdklab
2023-10-23 14:01 dpdklab
2023-10-23 13:58 dpdklab
2023-10-23 13:57 dpdklab
2023-10-23 13:57 dpdklab
2023-10-23 13:56 dpdklab
2023-10-23 13:56 dpdklab
2023-10-23 13:54 dpdklab
2023-10-23 13:53 dpdklab
2023-10-23 13:52 dpdklab
2023-10-23 13:52 dpdklab
2023-10-23 13:50 dpdklab
2023-10-23 13:49 dpdklab
2023-10-23 13:48 dpdklab
2023-10-23 13:48 dpdklab
2023-10-23 13:41 dpdklab
2023-10-23 13:41 dpdklab
2023-10-23 13:40 dpdklab
2023-10-23 13:37 dpdklab
2023-10-23 13:36 dpdklab
2023-10-23 13:36 dpdklab
2023-10-23 13:36 dpdklab
2023-10-23 13:36 dpdklab
2023-10-23 13:36 dpdklab
2023-10-23 13:36 dpdklab
2023-10-23 13:36 dpdklab
2023-10-23 13:35 dpdklab
2023-10-23 13:35 dpdklab
2023-10-23 13:34 dpdklab
2023-10-23 13:34 dpdklab
2023-10-23 13:34 dpdklab
2023-10-23 13:30 dpdklab
2023-10-23 13:29 dpdklab
2023-10-23 13:24 dpdklab
2023-10-23 13:21 dpdklab
2023-10-23 13:15 dpdklab
2023-10-23 13:14 dpdklab
2023-10-23 13:11 dpdklab
2023-10-23 13:08 dpdklab
2023-10-23 12:39 dpdklab
2023-10-23 12:32 dpdklab
2023-10-23 12:27 dpdklab
2023-10-23 12:23 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=6536773f.630a0220.d98ff.59a1SMTPIN_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).