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| pw154644 [PATCH v2 10/10] build: support Undefined Behavior Sanitizer
Date: Mon, 23 Jun 2025 11:45:54 -0400	[thread overview]
Message-ID: <20250623154554.351557-1-robot@bytheb.org> (raw)
In-Reply-To: <20250623135242.461965-11-david.marchand@redhat.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/154644/

_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15827129893

  parent reply	other threads:[~2025-06-23 15:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250623135242.461965-11-david.marchand@redhat.com>
2025-06-23 13:19 ` |SUCCESS| pw154635-154644 " qemudev
2025-06-23 13:24 ` qemudev
2025-06-23 13:53 ` |SUCCESS| pw154644 " checkpatch
2025-06-23 14:39 ` |SUCCESS| pw154635-154644 [PATCH] [v2,10/10] build: support Undefine dpdklab
2025-06-23 14:40 ` dpdklab
2025-06-23 14:42 ` |PENDING| " dpdklab
2025-06-23 14:44 ` dpdklab
2025-06-23 14:45 ` dpdklab
2025-06-23 14:55 ` |SUCCESS| " dpdklab
2025-06-23 15:02 ` |PENDING| " dpdklab
2025-06-23 15:13 ` dpdklab
2025-06-23 15:16 ` |SUCCESS| " dpdklab
2025-06-23 15:40 ` dpdklab
2025-06-23 15:41 ` dpdklab
2025-06-23 15:41 ` dpdklab
2025-06-23 15:42 ` dpdklab
2025-06-23 15:42 ` dpdklab
2025-06-23 15:42 ` dpdklab
2025-06-23 15:43 ` dpdklab
2025-06-23 15:43 ` dpdklab
2025-06-23 15:45 ` |WARNING| " dpdklab
2025-06-23 15:45 ` 0-day Robot [this message]
2025-06-23 16:01 ` |SUCCESS| " dpdklab
2025-06-23 16:10 ` |WARNING| " dpdklab
2025-06-23 17:35 ` |SUCCESS| " dpdklab
2025-06-23 18:10 ` dpdklab
2025-06-23 18:11 ` 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=20250623154554.351557-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).