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| pw138951 [PATCH v17 15/15] log: colorize log output
Date: Wed, 27 Mar 2024 20:25:22 -0400	[thread overview]
Message-ID: <20240328002522.3710767-1-robot@bytheb.org> (raw)
In-Reply-To: <20240327233001.83505-16-stephen@networkplumber.org>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-03-28  0:25 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240327233001.83505-16-stephen@networkplumber.org>
2024-03-27 23:08 ` |SUCCESS| pw138937-138951 " qemudev
2024-03-27 23:13 ` qemudev
2024-03-27 23:32 ` |SUCCESS| pw138951 " checkpatch
2024-03-28  0:25 ` 0-day Robot [this message]
2024-03-28 13:21 ` |FAILURE| pw138937-138951 [PATCH] [v17,15/15] log: colorize log outp dpdklab
2024-03-28 13:21 ` dpdklab
2024-03-28 13:21 ` |SUCCESS| " dpdklab
2024-03-28 13:21 ` |FAILURE| " dpdklab
2024-03-28 13:22 ` dpdklab
2024-03-28 13:22 ` dpdklab
2024-03-28 13:22 ` dpdklab
2024-03-28 13:22 ` |SUCCESS| " dpdklab
2024-03-28 13:23 ` dpdklab
2024-03-28 13:23 ` |FAILURE| " dpdklab
2024-03-28 13:29 ` |SUCCESS| " dpdklab
2024-03-28 13:30 ` dpdklab
2024-03-28 13:31 ` dpdklab
2024-03-28 13:33 ` dpdklab
2024-03-28 13:36 ` dpdklab
2024-03-28 13:37 ` dpdklab
2024-03-28 13:37 ` dpdklab
2024-03-28 13:38 ` dpdklab
2024-03-28 13:38 ` dpdklab
2024-03-28 13:38 ` dpdklab
2024-03-28 13:38 ` dpdklab
2024-03-28 13:38 ` |FAILURE| " dpdklab
2024-03-28 13:41 ` |SUCCESS| " dpdklab
2024-03-28 13:41 ` dpdklab
2024-03-28 13:42 ` dpdklab
2024-03-28 13:42 ` dpdklab
2024-03-28 13:42 ` dpdklab
2024-03-28 13:43 ` dpdklab
2024-03-28 13:43 ` dpdklab
2024-03-28 13:44 ` dpdklab
2024-03-28 13:45 ` dpdklab
2024-03-28 13:52 ` dpdklab
2024-03-28 13:54 ` dpdklab
2024-03-28 13:54 ` dpdklab
2024-03-28 13:55 ` dpdklab
2024-03-28 13:55 ` dpdklab
2024-03-28 13:55 ` dpdklab
2024-03-28 13:56 ` dpdklab
2024-03-28 13:57 ` |FAILURE| " dpdklab
2024-03-28 13:57 ` |SUCCESS| " dpdklab
2024-03-28 13:57 ` dpdklab
2024-03-28 13:57 ` |FAILURE| " dpdklab
2024-03-28 13:57 ` dpdklab
2024-03-28 13:57 ` dpdklab
2024-03-28 13:58 ` dpdklab
2024-03-28 13:59 ` |SUCCESS| " dpdklab
2024-03-28 13:59 ` dpdklab
2024-03-28 13:59 ` dpdklab
2024-03-28 14:00 ` |FAILURE| " dpdklab
2024-03-28 14:00 ` |SUCCESS| " dpdklab
2024-03-28 14:01 ` |FAILURE| " dpdklab
2024-03-28 14:03 ` dpdklab
2024-03-28 14:03 ` |SUCCESS| " dpdklab
2024-03-28 14:04 ` |FAILURE| " dpdklab
2024-03-28 14:04 ` |SUCCESS| " dpdklab
2024-03-28 14:06 ` |FAILURE| " dpdklab
2024-03-28 14:06 ` dpdklab
2024-03-28 14:07 ` dpdklab
2024-03-28 14:09 ` dpdklab
2024-03-28 14:11 ` dpdklab
2024-03-28 14:11 ` |SUCCESS| " dpdklab
2024-03-28 14:13 ` |FAILURE| " dpdklab
2024-03-28 14:19 ` |SUCCESS| " dpdklab
2024-03-28 14:20 ` dpdklab
2024-03-28 14:21 ` |FAILURE| " dpdklab
2024-03-28 14:28 ` dpdklab
2024-03-28 14:28 ` dpdklab
2024-03-28 14:29 ` dpdklab
2024-03-28 14:29 ` dpdklab
2024-03-28 14:30 ` dpdklab
2024-03-28 14:34 ` dpdklab
2024-03-28 14:34 ` |SUCCESS| " dpdklab
2024-03-28 14:35 ` dpdklab
2024-03-28 14:35 ` |FAILURE| " dpdklab
2024-03-28 14:35 ` dpdklab
2024-03-28 14:36 ` dpdklab
2024-03-28 14:38 ` |SUCCESS| " dpdklab
2024-03-28 14:49 ` |FAILURE| " dpdklab
2024-03-28 14:51 ` |SUCCESS| " dpdklab
2024-03-28 14:59 ` dpdklab
2024-03-28 15:01 ` dpdklab
2024-03-28 16:29 ` dpdklab
2024-04-02 15:32 ` dpdklab
2024-04-02 15:36 ` dpdklab
2024-04-02 15:40 ` dpdklab
2024-04-02 16:00 ` dpdklab
2024-04-02 16:04 ` 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=20240328002522.3710767-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).