automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw158325 [PATCH dpdk] graph: fix use-after-free when updating edges with active graphs
Date: Fri, 31 Oct 2025 19:17:21 -0400	[thread overview]
Message-ID: <20251031231721.1962701-1-robot@bytheb.org> (raw)
In-Reply-To: <20251031221304.394997-2-rjarry@redhat.com>

From: robot@bytheb.org

Test-Label: github-robot-post
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/158325/

_github post: success_
HTML Link: https://github.com/ovsrobot/dpdk/pull/292

  parent reply	other threads:[~2025-10-31 23:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251031221304.394997-2-rjarry@redhat.com>
2025-10-31 21:40 ` qemudev
2025-10-31 21:45 ` qemudev
2025-10-31 22:13 ` checkpatch
2025-10-31 22:41 ` |PENDING| pw158325 [PATCH] graph: fix use-after-free when updating e dpdklab
2025-10-31 22:42 ` dpdklab
2025-10-31 22:43 ` |SUCCESS| " dpdklab
2025-10-31 22:43 ` |PENDING| " dpdklab
2025-10-31 22:45 ` dpdklab
2025-10-31 22:47 ` |SUCCESS| " dpdklab
2025-10-31 22:50 ` |FAILURE| " dpdklab
2025-10-31 22:50 ` dpdklab
2025-10-31 22:51 ` |PENDING| " dpdklab
2025-10-31 22:59 ` |SUCCESS| " dpdklab
2025-10-31 23:03 ` dpdklab
2025-10-31 23:03 ` |WARNING| " dpdklab
2025-10-31 23:05 ` |SUCCESS| " dpdklab
2025-10-31 23:12 ` |WARNING| " dpdklab
2025-10-31 23:17 ` |SUCCESS| pw158325 [PATCH dpdk] graph: fix use-after-free when updating edges with active graphs 0-day Robot
2025-10-31 23:17 ` 0-day Robot [this message]
2025-10-31 23:23 ` |SUCCESS| pw158325 [PATCH] graph: fix use-after-free when updating e dpdklab
2025-10-31 23:25 ` dpdklab
2025-10-31 23:26 ` |WARNING| " dpdklab
2025-10-31 23:28 ` |SUCCESS| " dpdklab
2025-10-31 23:30 ` dpdklab
2025-11-01  0:16 ` dpdklab
2025-11-01  2:17 ` 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=20251031231721.1962701-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --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).