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| pw138457 [PATCH v2 3/3] dts: store stderr in RemoteCommandExecutionError
Date: Mon, 18 Mar 2024 14:03:30 -0400	[thread overview]
Message-ID: <20240318180330.3519870-1-robot@bytheb.org> (raw)
In-Reply-To: <20240318171704.798634-4-luca.vizzarro@arm.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-03-18 18:03 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240318171704.798634-4-luca.vizzarro@arm.com>
2024-03-18 16:55 ` |SUCCESS| pw138455-138457 " qemudev
2024-03-18 16:59 ` qemudev
2024-03-18 17:19 ` |SUCCESS| pw138457 " checkpatch
2024-03-18 17:51 ` |SUCCESS| pw138455-138457 [PATCH] [v2,3/3] dts: store stderr in Remo dpdklab
2024-03-18 17:51 ` dpdklab
2024-03-18 17:51 ` dpdklab
2024-03-18 17:51 ` dpdklab
2024-03-18 17:52 ` dpdklab
2024-03-18 17:52 ` dpdklab
2024-03-18 17:52 ` dpdklab
2024-03-18 17:53 ` dpdklab
2024-03-18 17:54 ` dpdklab
2024-03-18 17:54 ` dpdklab
2024-03-18 17:54 ` dpdklab
2024-03-18 17:55 ` dpdklab
2024-03-18 17:55 ` dpdklab
2024-03-18 17:55 ` dpdklab
2024-03-18 17:55 ` dpdklab
2024-03-18 17:56 ` dpdklab
2024-03-18 17:56 ` dpdklab
2024-03-18 17:56 ` dpdklab
2024-03-18 17:57 ` dpdklab
2024-03-18 17:57 ` dpdklab
2024-03-18 17:58 ` dpdklab
2024-03-18 17:58 ` dpdklab
2024-03-18 17:59 ` dpdklab
2024-03-18 17:59 ` dpdklab
2024-03-18 17:59 ` dpdklab
2024-03-18 17:59 ` dpdklab
2024-03-18 18:00 ` dpdklab
2024-03-18 18:00 ` dpdklab
2024-03-18 18:01 ` dpdklab
2024-03-18 18:03 ` 0-day Robot [this message]
2024-03-18 18:04 ` dpdklab
2024-03-18 18:04 ` dpdklab
2024-03-18 18:05 ` dpdklab
2024-03-18 18:06 ` dpdklab
2024-03-18 18:06 ` dpdklab
2024-03-18 18:06 ` dpdklab
2024-03-18 18:07 ` dpdklab
2024-03-18 18:07 ` dpdklab
2024-03-18 18:07 ` dpdklab
2024-03-18 18:07 ` dpdklab
2024-03-18 18:08 ` dpdklab
2024-03-18 18:08 ` dpdklab
2024-03-18 18:09 ` dpdklab
2024-03-18 18:09 ` dpdklab
2024-03-18 18:10 ` dpdklab
2024-03-18 18:10 ` dpdklab
2024-03-18 18:10 ` dpdklab
2024-03-18 18:11 ` dpdklab
2024-03-18 18:11 ` dpdklab
2024-03-18 18:12 ` dpdklab
2024-03-18 18:12 ` dpdklab
2024-03-18 18:12 ` dpdklab
2024-03-18 18:13 ` dpdklab
2024-03-18 18:13 ` dpdklab
2024-03-18 18:14 ` dpdklab
2024-03-18 18:15 ` dpdklab
2024-03-18 18:16 ` dpdklab
2024-03-18 18:16 ` dpdklab
2024-03-18 18:22 ` dpdklab
2024-03-18 18:23 ` dpdklab
2024-03-18 18:24 ` dpdklab
2024-03-18 18:24 ` dpdklab
2024-03-18 18:24 ` dpdklab
2024-03-18 18:24 ` dpdklab
2024-03-18 18:24 ` dpdklab
2024-03-18 18:27 ` dpdklab
2024-03-18 18:27 ` dpdklab
2024-03-18 18:27 ` dpdklab
2024-03-18 18:29 ` dpdklab
2024-03-18 18:30 ` dpdklab
2024-03-18 18:33 ` dpdklab
2024-03-18 19:15 ` dpdklab
2024-03-18 20:50 ` dpdklab
2024-03-18 21:26 ` dpdklab
2024-03-20 15:50 ` dpdklab
2024-03-20 16:22 ` 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=20240318180330.3519870-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).