automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144954 [PATCH v2] service: fix deadlock on worker lcore exit
Date: Thu, 3 Oct 2024 14:37:10 +0800	[thread overview]
Message-ID: <202410030637.4936bAid3155192@localhost.localdomain> (raw)
In-Reply-To: <20241003065702.3051158-1-david.marchand@redhat.com>

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

_Compilation OK_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Thu,  3 Oct 2024 08:57:02 +0200
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: c6a1564c27f9d4642cd07f1836480ad467116567

144954 --> 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:[~2024-10-03  7:06 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241003065702.3051158-1-david.marchand@redhat.com>
2024-10-03  6:37 ` qemudev [this message]
2024-10-03  6:41 ` |FAILURE| " qemudev
2024-10-03  6:58 ` |SUCCESS| " checkpatch
2024-10-03  7:45 ` |FAILURE| " 0-day Robot
2024-10-03  8:18 ` |SUCCESS| pw144954 [PATCH] [v2] service: fix deadlock on worker lcor dpdklab
2024-10-03  8:19 ` dpdklab
2024-10-03  8:23 ` dpdklab
2024-10-03  8:25 ` dpdklab
2024-10-03  8:28 ` dpdklab
2024-10-03  8:30 ` dpdklab
2024-10-03  8:32 ` dpdklab
2024-10-03  8:34 ` dpdklab
2024-10-03  8:47 ` dpdklab
2024-10-03  8:56 ` dpdklab
2024-10-03 10:03 ` dpdklab
2024-10-03 10:12 ` |PENDING| " dpdklab
2024-10-03 10:42 ` dpdklab
2024-10-03 10:51 ` |FAILURE| " dpdklab
2024-10-03 10:52 ` dpdklab
2024-10-03 11:00 ` dpdklab
2024-10-03 11:00 ` dpdklab
2024-10-03 11:03 ` dpdklab
2024-10-03 11:08 ` dpdklab
2024-10-03 12:15 ` dpdklab
2024-10-03 12:17 ` dpdklab
2024-10-03 12:19 ` dpdklab
2024-10-03 12:23 ` dpdklab
2024-10-03 12:25 ` |SUCCESS| " dpdklab
2024-10-03 12:31 ` |FAILURE| " dpdklab
2024-10-03 12:33 ` dpdklab
2024-10-03 12:34 ` dpdklab
2024-10-03 12:37 ` |SUCCESS| " dpdklab
2024-10-03 12:40 ` |FAILURE| " dpdklab
2024-10-03 12:43 ` dpdklab
2024-10-03 12:44 ` dpdklab
2024-10-03 12:46 ` dpdklab
2024-10-03 12:48 ` dpdklab
2024-10-03 12:52 ` dpdklab
2024-10-03 12:54 ` dpdklab
2024-10-03 12:55 ` dpdklab
2024-10-03 13:01 ` dpdklab
2024-10-03 13:28 ` |SUCCESS| " 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=202410030637.4936bAid3155192@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).