automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143830 [PATCH] Coverity issue: Failure to enqueue packets for cryptodev-scheduler_multicore can lead to program crashes Bugzilla ID: 1537
Date: Tue, 10 Sep 2024 00:21:50 +0800	[thread overview]
Message-ID: <202409091621.489GLoGx3043726@localhost.localdomain> (raw)
In-Reply-To: <tencent_2B74A585963C1CDA8C52C45C6236CA934705@qq.com>

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

_Compilation OK_

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

143830 --> 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-09 16:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_2B74A585963C1CDA8C52C45C6236CA934705@qq.com>
2024-09-09 16:21 ` qemudev [this message]
2024-09-09 16:26 ` qemudev
2024-09-09 16:50 ` |WARNING| " checkpatch
2024-09-09 17:45 ` |SUCCESS| pw143830 [PATCH] Coverity issue: Failure to enqueue packets for cryptodev-scheduler_multicore can lead to program crashes Bugzilla ID: 1537 Fixes: replace `pending_deq_ops` with `pending_enq_ops` Cc: stable@dpdk.org 0-day Robot
2024-09-09 23:57 ` |SUCCESS| pw143830 [PATCH] Coverity issue: Failure to enqueue packet dpdklab
2024-09-10  0:01 ` dpdklab
2024-09-10  0:40 ` dpdklab
2024-09-10  2:34 ` |PENDING| " dpdklab
2024-09-10  2:41 ` |SUCCESS| " dpdklab
2024-09-10  2:41 ` dpdklab
2024-09-10  2:43 ` dpdklab
2024-09-10  2:52 ` |PENDING| " dpdklab
2024-09-10  3:15 ` |SUCCESS| " dpdklab
2024-09-10  3:28 ` |PENDING| " dpdklab
2024-09-10  3:42 ` |SUCCESS| " dpdklab
2024-09-10  3:43 ` dpdklab
2024-09-10  3:43 ` dpdklab
2024-09-10  5:28 ` |PENDING| " dpdklab
2024-09-10  6:18 ` |SUCCESS| " dpdklab
2024-09-10  7:16 ` dpdklab
2024-09-10  7:32 ` dpdklab
2024-09-10  7:33 ` dpdklab
2024-09-10  7:42 ` dpdklab
2024-09-10  8:21 ` dpdklab
2024-09-10  8:50 ` dpdklab
2024-09-10  9:21 ` dpdklab
2024-09-10  9:25 ` dpdklab
2024-09-10 11:05 ` dpdklab
2024-09-10 15:19 ` dpdklab
2024-09-16 13:30 ` dpdklab
2024-09-17  7:06 ` 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=202409091621.489GLoGx3043726@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).