From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131507 [PATCH] [v2] eal: allow swapping of malloc heaps
Date: Fri, 15 Sep 2023 14:05:08 -0700 (PDT) [thread overview]
Message-ID: <6504c704.6b0a0220.0a26.9f30SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131507
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, September 15 2023 13:10:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e92ba1426914db1d224dd5e9a1743657681b8814
131507 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27621/
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-15 21:05 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 21:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-15 22:19 dpdklab
2023-09-15 22:17 dpdklab
2023-09-15 22:00 dpdklab
2023-09-15 21:59 dpdklab
2023-09-15 21:56 dpdklab
2023-09-15 21:31 dpdklab
2023-09-15 21:30 dpdklab
2023-09-15 21:28 dpdklab
2023-09-15 21:23 dpdklab
2023-09-15 21:22 dpdklab
2023-09-15 21:19 dpdklab
2023-09-15 21:18 dpdklab
2023-09-15 21:17 dpdklab
2023-09-15 21:14 dpdklab
2023-09-15 21:09 dpdklab
2023-09-15 21:08 dpdklab
2023-09-15 21:06 dpdklab
2023-09-15 21:05 dpdklab
2023-09-15 21:03 dpdklab
2023-09-15 21:03 dpdklab
2023-09-15 21:03 dpdklab
2023-09-15 21:00 dpdklab
2023-09-15 20:56 dpdklab
2023-09-15 20:50 dpdklab
2023-09-15 20:49 dpdklab
2023-09-15 20:46 dpdklab
2023-09-15 20:45 dpdklab
2023-09-15 20:41 dpdklab
2023-09-15 20:37 dpdklab
2023-09-15 20:35 dpdklab
2023-09-15 20:33 dpdklab
2023-09-15 20:31 dpdklab
2023-09-15 20:28 dpdklab
2023-09-15 20:22 dpdklab
2023-09-15 20:20 dpdklab
2023-09-15 20:20 dpdklab
2023-09-15 20:19 dpdklab
2023-09-15 20:18 dpdklab
2023-09-15 20:16 dpdklab
2023-09-15 20:16 dpdklab
2023-09-15 20:16 dpdklab
2023-09-15 20:11 dpdklab
2023-09-15 20:05 dpdklab
2023-09-15 20:03 dpdklab
2023-09-15 20:02 dpdklab
2023-09-15 20:01 dpdklab
2023-09-15 20:00 dpdklab
2023-09-15 19:56 dpdklab
2023-09-15 19:55 dpdklab
[not found] <20230915131015.820160-1-bruce.richardson@intel.com>
2023-09-15 12:51 ` |SUCCESS| pw131507 [PATCH v2] " qemudev
2023-09-15 12:55 ` qemudev
2023-09-15 13:11 ` checkpatch
2023-09-15 13:59 ` 0-day Robot
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=6504c704.6b0a0220.0a26.9f30SMTPIN_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).