automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143959 [PATCH] crypto/scheduler: fix crashes in scheduler_multicore due to incorrect variable usage
Date: Thu, 12 Sep 2024 00:05:46 +0800	[thread overview]
Message-ID: <202409111605.48BG5kNC417058@localhost.localdomain> (raw)
In-Reply-To: <tencent_98734034A30594BC001A8912CB3C7ED6CF05@qq.com>

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

_Compilation OK_

Submitter: Yong Liang <1269690261@qq.com>
Date: Thu, 12 Sep 2024 00:06:10 +0800
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: b3485f4293997d35b6daecc3437bb0c183a51fb3

143959 --> 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-09-11 16:34 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_98734034A30594BC001A8912CB3C7ED6CF05@qq.com>
2024-09-11 16:05 ` qemudev [this message]
2024-09-11 16:07 ` checkpatch
2024-09-11 16:10 ` qemudev
2024-09-11 17:05 ` 0-day Robot
2024-09-11 22:30 ` |SUCCESS| pw143959 [PATCH] crypto/scheduler: fix crashes in schedule dpdklab
2024-09-11 22:44 ` dpdklab
2024-09-11 22:45 ` dpdklab
2024-09-11 23:11 ` dpdklab
2024-09-11 23:41 ` dpdklab
2024-09-11 23:41 ` dpdklab
2024-09-12  0:31 ` dpdklab
2024-09-12  1:19 ` dpdklab
2024-09-12  1:44 ` |PENDING| " dpdklab
2024-09-12  1:51 ` |SUCCESS| " dpdklab
2024-09-12  1:51 ` dpdklab
2024-09-12  2:04 ` |PENDING| " dpdklab
2024-09-12  2:33 ` |SUCCESS| " dpdklab
2024-09-12  2:34 ` dpdklab
2024-09-12  2:46 ` dpdklab
2024-09-12  2:48 ` dpdklab
2024-09-12  3:01 ` |PENDING| " dpdklab
2024-09-12  3:12 ` |SUCCESS| " dpdklab
2024-09-12  3:13 ` dpdklab
2024-09-12  3:18 ` dpdklab
2024-09-12  3:23 ` dpdklab
2024-09-12  3:23 ` dpdklab
2024-09-12  3:24 ` |PENDING| " dpdklab
2024-09-12  3:43 ` |SUCCESS| " dpdklab
2024-09-12  3:43 ` dpdklab
2024-09-12  3:50 ` dpdklab
2024-09-12  3:58 ` dpdklab
2024-09-12  4:10 ` dpdklab
2024-09-12  4:28 ` dpdklab
2024-09-12  4:40 ` dpdklab
2024-09-12  4:43 ` dpdklab
2024-09-12  4:45 ` dpdklab
2024-09-12  4:50 ` dpdklab
2024-09-12  5:10 ` dpdklab
2024-09-12  6:13 ` dpdklab
2024-09-12  9:05 ` dpdklab
2024-09-12 13:15 ` dpdklab
2024-09-12 14:06 ` dpdklab
2024-09-15 12:44 ` dpdklab
2024-09-15 13:09 ` dpdklab
2024-09-15 17:49 ` dpdklab
2024-09-15 18:19 ` 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=202409111605.48BG5kNC417058@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).