automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125126-125127 [PATCH v4 2/2] eal: fix failure path race setting new thread affinity
Date: Wed, 15 Mar 2023 06:48:14 +0800	[thread overview]
Message-ID: <202303142248.32EMmE9I3163516@localhost.localdomain> (raw)
In-Reply-To: <1678834239-11569-3-git-send-email-roretzla@linux.microsoft.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125127

_Compilation OK_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tue, 14 Mar 2023 15:50:38 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: baf13c3135d0c5998fff7edc23fb89412dc89246

125126-125127 --> 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


       reply	other threads:[~2023-03-14 23:02 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1678834239-11569-3-git-send-email-roretzla@linux.microsoft.com>
2023-03-14 22:48 ` qemudev [this message]
2023-03-14 22:51 ` |SUCCESS| pw125127 " checkpatch
2023-03-14 22:52 ` |SUCCESS| pw125126-125127 " qemudev
2023-03-15  1:19 ` |SUCCESS| pw125127 " 0-day Robot
2023-03-14 23:32 |SUCCESS| pw125126-125127 [PATCH] [v4, " dpdklab
2023-03-14 23:35 dpdklab
2023-03-14 23:35 dpdklab
2023-03-14 23:37 dpdklab
2023-03-14 23:40 dpdklab
2023-03-14 23:42 dpdklab
2023-03-14 23:42 dpdklab
2023-03-14 23:44 dpdklab
2023-03-14 23:45 dpdklab
2023-03-14 23:47 dpdklab
2023-03-14 23:48 dpdklab
2023-03-14 23:53 dpdklab
2023-03-14 23:56 dpdklab
2023-03-15  0:00 dpdklab
2023-03-15  0:00 dpdklab
2023-03-15  0:01 dpdklab
2023-03-15  0:01 dpdklab
2023-03-15  0:04 dpdklab
2023-03-15  0:04 dpdklab
2023-03-15  0:13 dpdklab
2023-03-15  0:22 dpdklab
2023-03-15  0:34 dpdklab
2023-03-15  0:38 dpdklab
2023-03-15  3:51 dpdklab
2023-03-15  4:14 dpdklab
2023-03-15  4:27 dpdklab
2023-03-15  5:26 dpdklab
2023-03-16  7:20 dpdklab
2023-03-16  9:49 dpdklab
2023-03-16  9:57 dpdklab
2023-03-16  9:59 dpdklab
2023-03-16 10:04 dpdklab
2023-03-16 10:04 dpdklab
2023-03-16 10:12 dpdklab
2023-03-16 10:17 dpdklab
2023-03-16 10:18 dpdklab
2023-03-16 10:21 dpdklab
2023-03-16 10:29 dpdklab
2023-03-16 10:34 dpdklab
2023-03-16 10:36 dpdklab
2023-03-16 10:36 dpdklab
2023-03-17  3:55 dpdklab
2023-03-17  5:02 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=202303142248.32EMmE9I3163516@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).