From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130873 [PATCH] eal: fix memory initialization deadlock
Date: Wed, 30 Aug 2023 04:19:39 -0700 (PDT) [thread overview]
Message-ID: <64ef25cb.810a0220.3e75e.47d4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130873
_Testing PASS_
Submitter: Artemy Kovalyov <artemyko@nvidia.com>
Date: Wednesday, August 30 2023 10:33:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b7b8de26f34d39c8aaded44d8a468da5e68f19da
130873 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Debian Buster | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27472/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-30 11:19 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 11:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-30 13:40 dpdklab
2023-08-30 13:35 dpdklab
2023-08-30 13:31 dpdklab
2023-08-30 13:20 dpdklab
2023-08-30 13:03 dpdklab
2023-08-30 12:58 dpdklab
2023-08-30 12:51 dpdklab
2023-08-30 12:47 dpdklab
2023-08-30 12:44 dpdklab
2023-08-30 12:42 dpdklab
2023-08-30 12:23 dpdklab
2023-08-30 12:16 dpdklab
2023-08-30 12:15 dpdklab
2023-08-30 12:07 dpdklab
2023-08-30 12:06 dpdklab
2023-08-30 12:04 dpdklab
2023-08-30 12:03 dpdklab
2023-08-30 12:01 dpdklab
2023-08-30 11:59 dpdklab
2023-08-30 11:51 dpdklab
2023-08-30 11:49 dpdklab
2023-08-30 11:48 dpdklab
2023-08-30 11:46 dpdklab
2023-08-30 11:45 dpdklab
2023-08-30 11:43 dpdklab
2023-08-30 11:43 dpdklab
2023-08-30 11:43 dpdklab
2023-08-30 11:36 dpdklab
2023-08-30 11:27 dpdklab
2023-08-30 11:25 dpdklab
2023-08-30 11:25 dpdklab
2023-08-30 11:25 dpdklab
2023-08-30 11:23 dpdklab
2023-08-30 11:22 dpdklab
2023-08-30 11:21 dpdklab
2023-08-30 11:18 dpdklab
2023-08-30 11:18 dpdklab
2023-08-30 11:14 dpdklab
2023-08-30 11:13 dpdklab
2023-08-30 11:11 dpdklab
2023-08-30 11:10 dpdklab
2023-08-30 11:09 dpdklab
2023-08-30 11:07 dpdklab
2023-08-30 11:07 dpdklab
2023-08-30 11:06 dpdklab
2023-08-30 11:05 dpdklab
2023-08-30 11:03 dpdklab
2023-08-30 11:02 dpdklab
[not found] <20230830103303.2428995-1-artemyko@nvidia.com>
2023-08-30 10:26 ` qemudev
2023-08-30 10:30 ` qemudev
2023-08-30 10:34 ` checkpatch
2023-08-30 11:39 ` 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=64ef25cb.810a0220.3e75e.47d4SMTPIN_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).