From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131163 [PATCH] malloc: fix allocation for a specific cas
Date: Tue, 05 Sep 2023 02:06:08 -0700 (PDT) [thread overview]
Message-ID: <64f6ef80.810a0220.bf22d.8873SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131163
_Testing PASS_
Submitter: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
Date: Monday, September 04 2023 14:24:32
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:799d56f1192d72872e63fbb3d2c7f776b7ae89b0
131163 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
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/27524/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-05 9:06 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 9:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-05 23:02 dpdklab
2023-09-05 22:57 dpdklab
2023-09-05 22:53 dpdklab
2023-09-05 22:42 dpdklab
2023-09-05 10:00 dpdklab
2023-09-05 9:41 dpdklab
2023-09-05 9:23 dpdklab
2023-09-05 9:20 dpdklab
2023-09-05 9:12 dpdklab
2023-09-05 9:12 dpdklab
2023-09-05 9:12 dpdklab
2023-09-05 9:12 dpdklab
2023-09-05 9:11 dpdklab
2023-09-05 9:10 dpdklab
2023-09-05 9:10 dpdklab
2023-09-05 9:10 dpdklab
2023-09-05 9:10 dpdklab
2023-09-05 9:09 dpdklab
2023-09-05 9:09 dpdklab
2023-09-05 9:05 dpdklab
2023-09-05 9:04 dpdklab
2023-09-05 9:04 dpdklab
2023-09-05 8:59 dpdklab
2023-09-05 8:57 dpdklab
2023-09-05 8:57 dpdklab
2023-09-05 8:53 dpdklab
2023-09-05 8:53 dpdklab
2023-09-05 8:50 dpdklab
2023-09-05 8:50 dpdklab
2023-09-05 8:50 dpdklab
2023-09-05 8:49 dpdklab
2023-09-05 8:48 dpdklab
2023-09-05 8:48 dpdklab
2023-09-05 8:48 dpdklab
2023-09-05 8:48 dpdklab
2023-09-05 8:47 dpdklab
2023-09-05 8:47 dpdklab
2023-09-05 8:47 dpdklab
2023-09-05 8:47 dpdklab
2023-09-05 8:43 dpdklab
2023-09-05 8:42 dpdklab
2023-09-05 8:42 dpdklab
2023-09-05 8:41 dpdklab
2023-09-05 8:41 dpdklab
2023-09-05 8:37 dpdklab
2023-09-05 8:37 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=64f6ef80.810a0220.bf22d.8873SMTPIN_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).