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| pw143994 [PATCH v2 14/14] drivers: use per line logging in helpers
Date: Thu, 12 Sep 2024 05:24:23 -0400	[thread overview]
Message-ID: <20240912092423.983939-1-robot@bytheb.org> (raw)
In-Reply-To: <20240912082643.1532679-15-david.marchand@redhat.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-09-12  9:24 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240912082643.1532679-15-david.marchand@redhat.com>
2024-09-12  8:04 ` |SUCCESS| pw143982-143994 " qemudev
2024-09-12  8:09 ` qemudev
2024-09-12  8:31 ` |WARNING| pw143994 " checkpatch
2024-09-12  9:24 ` 0-day Robot [this message]
2024-09-12 10:51 ` |SUCCESS| pw143982-143994 [PATCH] [v2,14/14] drivers: use per line l dpdklab
2024-09-12 11:03 ` dpdklab
2024-09-12 11:09 ` dpdklab
2024-09-12 11:39 ` dpdklab
2024-09-12 16:04 ` |PENDING| " dpdklab
2024-09-12 16:33 ` dpdklab
2024-09-12 17:01 ` dpdklab
2024-09-12 17:44 ` |SUCCESS| " dpdklab
2024-09-12 17:53 ` dpdklab
2024-09-12 17:55 ` dpdklab
2024-09-12 18:34 ` dpdklab
2024-09-12 18:38 ` dpdklab
2024-09-12 18:43 ` dpdklab
2024-09-12 19:03 ` |FAILURE| " dpdklab
2024-09-12 20:03 ` |SUCCESS| " dpdklab
2024-09-12 20:33 ` dpdklab
2024-09-12 21:17 ` |FAILURE| " dpdklab
2024-09-12 23:42 ` |SUCCESS| " dpdklab
2024-09-15  7:12 ` dpdklab
2024-09-15 11:53 ` |FAILURE| " dpdklab
2024-09-16 15:42 ` |SUCCESS| " dpdklab
2024-09-16 15:58 ` dpdklab
2024-09-16 15:59 ` |FAILURE| " dpdklab
2024-09-16 16:01 ` dpdklab
2024-09-16 16:08 ` |SUCCESS| " dpdklab
2024-09-16 16:13 ` dpdklab
2024-09-16 16:20 ` dpdklab
2024-09-16 16:32 ` dpdklab
2024-09-17 14:57 ` dpdklab
2024-09-17 23:41 ` dpdklab
2024-09-18  7:41 ` 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=20240912092423.983939-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).