From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124556 [PATCH] eal: fix thread race in control thread creation
Date: Mon, 27 Feb 2023 22:25:37 +0000 (UTC) [thread overview]
Message-ID: <20230227222537.4782A601B1@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/124556
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Monday, February 27 2023 17:17:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7710b5d15a014872a3aaf646668dafa928ca8473
124556 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25555/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-27 22:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 22:25 dpdklab [this message]
[not found] <1677518230-1194-1-git-send-email-roretzla@linux.microsoft.com>
2023-02-27 17:17 ` checkpatch
2023-02-27 19:39 ` 0-day Robot
2023-03-01 8:21 ` qemudev
2023-03-01 8:21 ` qemudev
-- strict thread matches above, loose matches on Subject: below --
2023-02-27 23:27 dpdklab
2023-02-27 23:22 dpdklab
2023-02-27 23:01 dpdklab
2023-02-27 23:01 dpdklab
2023-02-27 22:49 dpdklab
2023-02-27 22:46 dpdklab
2023-02-27 22:44 dpdklab
2023-02-27 22:39 dpdklab
2023-02-27 22:37 dpdklab
2023-02-27 22:37 dpdklab
2023-02-27 22:31 dpdklab
2023-02-27 22:18 dpdklab
2023-02-27 22:16 dpdklab
2023-02-27 22:16 dpdklab
2023-02-27 22:14 dpdklab
2023-02-27 22:05 dpdklab
2023-02-27 19:31 dpdklab
2023-02-27 18:37 dpdklab
2023-02-27 18:17 dpdklab
2023-02-27 18:08 dpdklab
2023-02-27 18:04 dpdklab
2023-02-27 18:02 dpdklab
2023-02-27 17:58 dpdklab
2023-02-27 17:56 dpdklab
2023-02-27 17:52 dpdklab
2023-02-27 17:51 dpdklab
2023-02-27 17:47 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=20230227222537.4782A601B1@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).