From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124736-124735 [PATCH 2/2] eal/windows: fix create thread failure behavior
Date: Mon, 6 Mar 2023 15:16:27 +0800 [thread overview]
Message-ID: <202303060716.3267GRhs3957674@localhost.localdomain> (raw)
In-Reply-To: <1677782682-27200-2-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124735
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thu, 2 Mar 2023 10:44:41 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124736-124735 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next prev parent reply other threads:[~2023-03-06 7:30 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1677782682-27200-2-git-send-email-roretzla@linux.microsoft.com>
2023-03-02 18:46 ` |SUCCESS| pw124735 " checkpatch
2023-03-02 20:39 ` 0-day Robot
2023-03-06 7:16 ` qemudev [this message]
2023-03-06 7:16 ` |SUCCESS| pw124736-124735 " qemudev
2023-03-03 6:23 |SUCCESS| pw124736-124735 [PATCH] [2/2] " dpdklab
2023-03-03 6:26 dpdklab
2023-03-03 6:27 dpdklab
2023-03-03 6:34 dpdklab
2023-03-03 6:34 dpdklab
2023-03-03 6:35 dpdklab
2023-03-03 6:38 dpdklab
2023-03-03 6:40 dpdklab
2023-03-03 6:53 dpdklab
2023-03-03 6:57 dpdklab
2023-03-03 7:00 dpdklab
2023-03-03 7:04 dpdklab
2023-03-03 7:05 dpdklab
2023-03-03 7:06 dpdklab
2023-03-03 7:07 dpdklab
2023-03-03 7:09 dpdklab
2023-03-03 7:09 dpdklab
2023-03-03 7:12 dpdklab
2023-03-03 7:14 dpdklab
2023-03-03 7:21 dpdklab
2023-03-03 7:21 dpdklab
2023-03-03 7:24 dpdklab
2023-03-03 7:34 dpdklab
2023-03-03 7:36 dpdklab
2023-03-03 7:54 dpdklab
2023-03-03 12:55 dpdklab
2023-03-03 14:53 dpdklab
2023-03-03 15:35 dpdklab
2023-03-03 16:04 dpdklab
2023-03-03 22:35 dpdklab
2023-03-03 23:44 dpdklab
2023-03-04 21:09 dpdklab
2023-03-04 21:23 dpdklab
2023-03-04 21:25 dpdklab
2023-03-04 21:30 dpdklab
2023-03-04 21:33 dpdklab
2023-03-04 21:37 dpdklab
2023-03-04 21:37 dpdklab
2023-03-04 21:56 dpdklab
2023-03-04 21:57 dpdklab
2023-03-04 22:02 dpdklab
2023-03-04 22:03 dpdklab
2023-03-04 22:08 dpdklab
2023-03-04 22:10 dpdklab
2023-03-04 22:10 dpdklab
2023-03-04 22:13 dpdklab
2023-03-04 22:15 dpdklab
2023-03-04 22:19 dpdklab
2023-03-04 22:20 dpdklab
2023-03-04 22:21 dpdklab
2023-03-04 22:25 dpdklab
2023-03-04 22:27 dpdklab
2023-03-04 22:29 dpdklab
2023-03-04 22:31 dpdklab
2023-03-04 22:35 dpdklab
2023-03-04 22:56 dpdklab
2023-03-04 22:56 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=202303060716.3267GRhs3957674@localhost.localdomain \
--to=qemudev@loongson.cn \
--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).