automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw150807 [PATCH] stack: occasional crash due to uninitialized variable
Date: Tue, 4 Feb 2025 09:08:48 +0800	[thread overview]
Message-ID: <202502040108.51418m9p992208@localhost.localdomain> (raw)
In-Reply-To: <1738632218-5796-1-git-send-email-andremue@linux.microsoft.com>

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

_Compilation OK_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Mon,  3 Feb 2025 17:23:37 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: dc4ce7c2538b713e16887eb598da309bc7b4d528

150807 --> 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:[~2025-02-04  1:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1738632218-5796-1-git-send-email-andremue@linux.microsoft.com>
2025-02-04  1:08 ` qemudev [this message]
2025-02-04  1:13 ` qemudev
2025-02-04  1:23 ` checkpatch
2025-02-04  2:15 ` |SUCCESS| pw150807 [PATCH] stack: occasional crash due to uninitiali dpdklab
2025-02-04  2:23 ` |SUCCESS| pw150807 [PATCH] stack: occasional crash due to uninitialized variable 0-day Robot
2025-02-04  2:25 ` |PENDING| pw150807 [PATCH] stack: occasional crash due to uninitiali dpdklab
2025-02-04  2:27 ` dpdklab
2025-02-04  2:31 ` |SUCCESS| " dpdklab
2025-02-04  2:42 ` |PENDING| " dpdklab
2025-02-04  3:04 ` dpdklab
2025-02-04  3:48 ` |SUCCESS| " dpdklab
2025-02-04  3:49 ` dpdklab
2025-02-04  3:57 ` dpdklab
2025-02-04  3:57 ` dpdklab
2025-02-04  4:11 ` dpdklab
2025-02-04  4:12 ` dpdklab
2025-02-04  5:29 ` dpdklab
2025-02-04  5:54 ` 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=202502040108.51418m9p992208@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).