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| pw152262 [RFC] eal: add new function versioning macros
Date: Wed,  5 Mar 2025 17:43:59 -0500	[thread overview]
Message-ID: <20250305224359.2592405-1-robot@bytheb.org> (raw)
In-Reply-To: <20250305212349.2036410-1-david.marchand@redhat.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2025-03-05 22:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250305212349.2036410-1-david.marchand@redhat.com>
2025-03-05 20:49 ` qemudev
2025-03-05 20:53 ` qemudev
2025-03-05 22:27 ` |SUCCESS| pw152262 [PATCH] [RFC] eal: add new function versioning ma dpdklab
2025-03-05 22:33 ` |FAILURE| " dpdklab
2025-03-05 22:34 ` |SUCCESS| " dpdklab
2025-03-05 22:43 ` 0-day Robot [this message]
2025-03-05 22:53 ` dpdklab
2025-03-05 22:54 ` |FAILURE| " dpdklab
2025-03-05 23:00 ` dpdklab
2025-03-05 23:04 ` |SUCCESS| " dpdklab
2025-03-05 23:13 ` |PENDING| " dpdklab
2025-03-05 23:14 ` dpdklab
2025-03-05 23:46 ` |SUCCESS| " dpdklab
2025-03-05 23:49 ` dpdklab
2025-03-06  0:02 ` dpdklab
2025-03-06  0:14 ` dpdklab
2025-03-06  0:17 ` |FAILURE| " dpdklab
2025-03-06  1:46 ` |SUCCESS| " dpdklab
2025-03-06  2:37 ` dpdklab
2025-03-06  2:37 ` dpdklab
2025-03-06  2:47 ` dpdklab
2025-03-06  2:54 ` dpdklab
2025-03-06  4:19 ` dpdklab
2025-03-06  4:53 ` dpdklab
2025-03-06  6:16 ` |FAILURE| " dpdklab
2025-03-06  6:20 ` |SUCCESS| " dpdklab
2025-03-06  7:17 ` dpdklab
2025-03-06  7:40 ` dpdklab
2025-03-06  7:40 ` dpdklab
2025-03-06  8:28 ` dpdklab
2025-03-06  8:39 ` dpdklab
2025-03-06 11: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=20250305224359.2592405-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).