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| pw143785 [PATCH 11/11] drivers: use per line logging in helpers
Date: Sat,  7 Sep 2024 11:44:52 -0400	[thread overview]
Message-ID: <20240907154452.980231-1-robot@bytheb.org> (raw)
In-Reply-To: <20240907145433.1479091-12-david.marchand@redhat.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-09-07 15:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240907145433.1479091-12-david.marchand@redhat.com>
2024-09-07 14:30 ` |SUCCESS| pw143775-143785 " qemudev
2024-09-07 14:35 ` qemudev
2024-09-07 14:57 ` |WARNING| pw143785 " checkpatch
2024-09-07 15:44 ` 0-day Robot [this message]
2024-09-09 21:51 ` |SUCCESS| pw143775-143785 [PATCH] [11/11] drivers: use per line logg dpdklab
2024-09-09 22:12 ` dpdklab
2024-09-09 22:33 ` dpdklab
2024-09-09 22:50 ` |PENDING| " dpdklab
2024-09-09 22:50 ` dpdklab
2024-09-09 23:02 ` |SUCCESS| " dpdklab
2024-09-09 23:03 ` dpdklab
2024-09-09 23:32 ` |PENDING| " dpdklab
2024-09-10  0:33 ` |FAILURE| " dpdklab
2024-09-10  0:37 ` dpdklab
2024-09-10  1:11 ` |WARNING| " dpdklab
2024-09-10  2:01 ` |PENDING| " dpdklab
2024-09-10  3:31 ` |FAILURE| " dpdklab
2024-09-10  3:57 ` |SUCCESS| " dpdklab
2024-09-10  4:32 ` |WARNING| " dpdklab
2024-09-10  5:25 ` |SUCCESS| " dpdklab
2024-09-10  5:30 ` dpdklab
2024-09-10  5:35 ` dpdklab
2024-09-10  5:48 ` |FAILURE| " dpdklab
2024-09-10  5:55 ` dpdklab
2024-09-10  6:02 ` |SUCCESS| " dpdklab
2024-09-10 13:44 ` dpdklab
2024-09-16  7:39 ` dpdklab
2024-09-16 15:31 ` |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=20240907154452.980231-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).