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| pw144607 [PATCH v2 16/16] eal: add alloc_function attribute to rte_malloc
Date: Sat, 28 Sep 2024 13:43:50 -0400	[thread overview]
Message-ID: <20240928174350.3044763-1-robot@bytheb.org> (raw)
In-Reply-To: <20240928164814.861933-17-stephen@networkplumber.org>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-09-28 17:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240928164814.861933-17-stephen@networkplumber.org>
2024-09-28 16:23 ` |SUCCESS| pw144592-144607 " qemudev
2024-09-28 16:28 ` qemudev
2024-09-28 16:51 ` |SUCCESS| pw144607 " checkpatch
2024-09-28 17:43 ` 0-day Robot [this message]
2024-09-28 22:08 ` |SUCCESS| pw144592-144607 [PATCH] [v2,16/16] eal: add alloc_function dpdklab
2024-09-28 22:15 ` dpdklab
2024-09-28 22:17 ` dpdklab
2024-09-28 22:20 ` dpdklab
2024-09-28 22:25 ` dpdklab
2024-09-28 22:34 ` dpdklab
2024-09-28 22:47 ` |PENDING| " dpdklab
2024-09-28 22:47 ` |FAILURE| " dpdklab
2024-09-28 22:48 ` dpdklab
2024-09-28 22:48 ` dpdklab
2024-09-28 22:49 ` |SUCCESS| " dpdklab
2024-09-28 22:59 ` dpdklab
2024-09-28 23:02 ` |PENDING| " dpdklab
2024-09-28 23:12 ` dpdklab
2024-09-28 23:14 ` |SUCCESS| " dpdklab
2024-09-28 23:39 ` |FAILURE| " dpdklab
2024-09-28 23:40 ` |SUCCESS| " dpdklab
2024-09-28 23:42 ` |FAILURE| " dpdklab
2024-09-28 23:53 ` |WARNING| " dpdklab
2024-09-29  0:08 ` |FAILURE| " dpdklab
2024-09-29  0:16 ` |SUCCESS| " dpdklab
2024-09-29  2:00 ` |WARNING| " dpdklab
2024-09-29  4:19 ` |FAILURE| " 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=20240928174350.3044763-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).