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| pw142450 [PATCH v2 2/2] dts: add dual_vlan test suite to the yaml schema
Date: Tue, 16 Jul 2024 18:23:52 -0400	[thread overview]
Message-ID: <20240716222352.2156988-1-robot@bytheb.org> (raw)
In-Reply-To: <20240716212416.444577-3-jspewock@iol.unh.edu>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-07-16 22:23 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240716212416.444577-3-jspewock@iol.unh.edu>
2024-07-16 20:59 ` |SUCCESS| pw142449-142450 " qemudev
2024-07-16 21:04 ` qemudev
2024-07-16 21:26 ` |SUCCESS| pw142450 " checkpatch
2024-07-16 22:23 ` 0-day Robot [this message]
2024-07-17  7:14 ` |SUCCESS| pw142449-142450 [PATCH] [v2,2/2] dts: add dual_vlan test s dpdklab
2024-07-17  7:17 ` |PENDING| " dpdklab
2024-07-17  7:18 ` dpdklab
2024-07-17  7:19 ` |SUCCESS| " dpdklab
2024-07-17  7:20 ` |PENDING| " dpdklab
2024-07-17  7:21 ` dpdklab
2024-07-17  7:23 ` dpdklab
2024-07-17  7:24 ` dpdklab
2024-07-17  7:26 ` dpdklab
2024-07-17  7:27 ` dpdklab
2024-07-17  7:30 ` dpdklab
2024-07-17  7:33 ` |SUCCESS| " dpdklab
2024-07-17  7:35 ` |PENDING| " dpdklab
2024-07-17  7:39 ` dpdklab
2024-07-17  7:40 ` dpdklab
2024-07-17  7:40 ` dpdklab
2024-07-17  7:41 ` dpdklab
2024-07-17  7:42 ` dpdklab
2024-07-17  7:43 ` |SUCCESS| " dpdklab
2024-07-17  7:46 ` |PENDING| " dpdklab
2024-07-17  7:49 ` |SUCCESS| " dpdklab
2024-07-17  7:53 ` dpdklab
2024-07-17  8:36 ` dpdklab
2024-07-17  8:52 ` dpdklab
2024-07-17  9:29 ` dpdklab
2024-07-17  9:37 ` dpdklab
2024-07-17 10:13 ` dpdklab
2024-07-17 10:28 ` |PENDING| " dpdklab
2024-07-17 10:37 ` |SUCCESS| " dpdklab
2024-07-17 10:37 ` dpdklab
2024-07-17 11:03 ` |PENDING| " dpdklab
2024-07-17 11:04 ` dpdklab
2024-07-17 11:04 ` dpdklab
2024-07-17 11:04 ` dpdklab
2024-07-17 11:05 ` dpdklab
2024-07-17 11:05 ` dpdklab
2024-07-17 11:05 ` dpdklab
2024-07-17 11:05 ` dpdklab
2024-07-17 11:20 ` dpdklab
2024-07-17 11:21 ` dpdklab
2024-07-17 11:22 ` dpdklab
2024-07-17 11:22 ` dpdklab
2024-07-17 11:28 ` dpdklab
2024-07-17 11:39 ` dpdklab
2024-07-17 11:40 ` dpdklab
2024-07-17 11:40 ` dpdklab
2024-07-17 11:45 ` dpdklab
2024-07-17 11:48 ` dpdklab
2024-07-17 11:50 ` dpdklab
2024-07-17 11:51 ` dpdklab
2024-07-17 11:53 ` dpdklab
2024-07-17 12:05 ` dpdklab
2024-07-17 12:21 ` dpdklab
2024-07-17 12:22 ` |SUCCESS| " dpdklab
2024-07-17 12:44 ` dpdklab
2024-07-17 14:39 ` 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=20240716222352.2156988-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).