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| pw124619 [PATCH] [v2] eal: fix thread race in control thread creation
Date: Thu, 2 Mar 2023 02:37:55 +0000 (UTC) [thread overview]
Message-ID: <20230302023755.3075D601F7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124619
_Functional Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, March 01 2023 21:09:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124619 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25581/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-02 2:37 UTC|newest]
Thread overview: 145+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 2:37 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-03 16:09 dpdklab
2023-03-03 16:09 dpdklab
2023-03-03 15:35 dpdklab
2023-03-03 15:33 dpdklab
2023-03-03 15:30 dpdklab
2023-03-03 15:27 dpdklab
2023-03-03 15:24 dpdklab
2023-03-03 15:21 dpdklab
2023-03-03 15:20 dpdklab
2023-03-03 15:17 dpdklab
2023-03-03 15:13 dpdklab
2023-03-03 15:11 dpdklab
2023-03-03 15:11 dpdklab
2023-03-03 15:10 dpdklab
2023-03-03 15:10 dpdklab
2023-03-03 15:03 dpdklab
2023-03-03 14:18 dpdklab
2023-03-03 14:18 dpdklab
2023-03-03 14:17 dpdklab
2023-03-03 14:16 dpdklab
2023-03-03 14:13 dpdklab
2023-03-03 14:01 dpdklab
2023-03-03 14:01 dpdklab
2023-03-03 14:00 dpdklab
2023-03-03 13:59 dpdklab
2023-03-03 13:58 dpdklab
2023-03-03 13:55 dpdklab
2023-03-03 13:48 dpdklab
2023-03-03 13:47 dpdklab
2023-03-03 13:30 dpdklab
2023-03-03 13:29 dpdklab
2023-03-03 13:27 dpdklab
2023-03-03 13:23 dpdklab
2023-03-03 13:11 dpdklab
2023-03-03 13:09 dpdklab
2023-03-03 13:09 dpdklab
2023-03-03 12:58 dpdklab
2023-03-03 12:55 dpdklab
2023-03-03 12:48 dpdklab
2023-03-03 12:48 dpdklab
2023-03-03 12:39 dpdklab
2023-03-03 12:36 dpdklab
2023-03-03 12:19 dpdklab
2023-03-03 12:18 dpdklab
2023-03-03 12:18 dpdklab
2023-03-03 12:17 dpdklab
2023-03-03 12:15 dpdklab
2023-03-03 12:14 dpdklab
2023-03-03 12:07 dpdklab
2023-03-03 12:05 dpdklab
2023-03-03 12:05 dpdklab
2023-03-03 12:02 dpdklab
2023-03-03 11:56 dpdklab
2023-03-03 11:55 dpdklab
2023-03-03 10:40 dpdklab
2023-03-03 10:40 dpdklab
2023-03-03 10:10 dpdklab
2023-03-03 9:54 dpdklab
2023-03-03 9:53 dpdklab
2023-03-03 9:51 dpdklab
2023-03-03 9:46 dpdklab
2023-03-03 9:40 dpdklab
2023-03-03 9:33 dpdklab
2023-03-03 9:30 dpdklab
2023-03-03 9:28 dpdklab
2023-03-03 9:22 dpdklab
2023-03-03 9:07 dpdklab
2023-03-02 16:46 dpdklab
2023-03-02 16:03 dpdklab
2023-03-02 15:41 dpdklab
2023-03-02 14:46 dpdklab
2023-03-02 13:25 dpdklab
2023-03-02 12:14 dpdklab
2023-03-02 12:12 dpdklab
2023-03-02 11:33 dpdklab
2023-03-02 11:31 dpdklab
2023-03-02 10:44 dpdklab
2023-03-02 7:16 dpdklab
2023-03-02 7:04 dpdklab
2023-03-02 6:44 dpdklab
2023-03-02 6:32 dpdklab
2023-03-02 6:26 dpdklab
2023-03-02 6:14 dpdklab
2023-03-02 6:12 dpdklab
2023-03-02 5:59 dpdklab
2023-03-02 5:58 dpdklab
2023-03-02 5:45 dpdklab
2023-03-02 5:39 dpdklab
2023-03-02 5:29 dpdklab
2023-03-02 5:26 dpdklab
2023-03-02 5:16 dpdklab
2023-03-02 5:00 dpdklab
2023-03-02 4:48 dpdklab
2023-03-02 4:34 dpdklab
2023-03-02 4:22 dpdklab
2023-03-02 4:03 dpdklab
2023-03-02 3:46 dpdklab
2023-03-02 3:31 dpdklab
2023-03-02 3:15 dpdklab
2023-03-02 3:15 dpdklab
2023-03-02 3:15 dpdklab
2023-03-02 3:15 dpdklab
2023-03-02 3:14 dpdklab
2023-03-02 3:11 dpdklab
2023-03-02 3:04 dpdklab
2023-03-02 2:43 dpdklab
2023-03-02 2:30 dpdklab
2023-03-02 2:18 dpdklab
2023-03-02 2:16 dpdklab
2023-03-02 2:10 dpdklab
2023-03-02 2:10 dpdklab
2023-03-02 2:10 dpdklab
2023-03-02 2:06 dpdklab
2023-03-02 2:03 dpdklab
2023-03-02 1:58 dpdklab
2023-03-02 1:52 dpdklab
2023-03-02 1:50 dpdklab
2023-03-02 1:50 dpdklab
2023-03-02 1:40 dpdklab
2023-03-02 1:37 dpdklab
2023-03-02 1:36 dpdklab
2023-03-02 1:32 dpdklab
2023-03-02 1:29 dpdklab
2023-03-02 1:28 dpdklab
2023-03-02 1:24 dpdklab
2023-03-02 1:17 dpdklab
2023-03-02 1:13 dpdklab
2023-03-02 1:09 dpdklab
2023-03-02 1:07 dpdklab
2023-03-02 1:06 dpdklab
2023-03-02 0:45 dpdklab
2023-03-02 0:40 dpdklab
2023-03-02 0:33 dpdklab
2023-03-02 0:32 dpdklab
2023-03-02 0:29 dpdklab
2023-03-02 0:28 dpdklab
2023-03-02 0:18 dpdklab
2023-03-02 0:17 dpdklab
2023-03-02 0:05 dpdklab
2023-03-01 23:36 dpdklab
[not found] <1677704982-2643-1-git-send-email-roretzla@linux.microsoft.com>
2023-03-01 21:02 ` |SUCCESS| pw124619 [PATCH v2] " qemudev
2023-03-01 21:06 ` qemudev
2023-03-01 21:11 ` checkpatch
2023-03-01 22: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=20230302023755.3075D601F7@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).