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| pw143117 [PATCH v6 4/4] test: restore cfgfile tests
Date: Tue, 13 Aug 2024 13:02:34 -0400	[thread overview]
Message-ID: <20240813170234.3855030-1-robot@bytheb.org> (raw)
In-Reply-To: <20240813160039.5861-5-stephen@networkplumber.org>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-08-13 17:02 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240813160039.5861-5-stephen@networkplumber.org>
2024-08-13 15:42 ` |SUCCESS| pw143114-143117 " qemudev
2024-08-13 15:47 ` qemudev
2024-08-13 16:02 ` |SUCCESS| pw143117 " checkpatch
2024-08-13 17:02 ` 0-day Robot [this message]
2024-08-13 18:39 ` |SUCCESS| pw143114-143117 [PATCH] [v6,4/4] test: restore cfgfile tes dpdklab
2024-08-13 18:42 ` |PENDING| " dpdklab
2024-08-13 18:44 ` |SUCCESS| " dpdklab
2024-08-13 18:45 ` |PENDING| " dpdklab
2024-08-13 18:45 ` dpdklab
2024-08-13 18:48 ` |SUCCESS| " dpdklab
2024-08-13 18:49 ` dpdklab
2024-08-13 18:49 ` |PENDING| " dpdklab
2024-08-13 18:50 ` dpdklab
2024-08-13 18:51 ` dpdklab
2024-08-13 18:51 ` dpdklab
2024-08-13 18:52 ` dpdklab
2024-08-13 18:52 ` dpdklab
2024-08-13 18:53 ` dpdklab
2024-08-13 18:53 ` dpdklab
2024-08-13 18:54 ` dpdklab
2024-08-13 18:54 ` dpdklab
2024-08-13 18:54 ` dpdklab
2024-08-13 18:54 ` |SUCCESS| " dpdklab
2024-08-13 18:55 ` |PENDING| " dpdklab
2024-08-13 18:55 ` dpdklab
2024-08-13 18:56 ` dpdklab
2024-08-13 18:56 ` dpdklab
2024-08-13 18:56 ` dpdklab
2024-08-13 18:57 ` |SUCCESS| " dpdklab
2024-08-13 18:57 ` |PENDING| " dpdklab
2024-08-13 18:57 ` dpdklab
2024-08-13 18:57 ` |SUCCESS| " dpdklab
2024-08-13 18:59 ` dpdklab
2024-08-13 19:00 ` |PENDING| " dpdklab
2024-08-13 19:00 ` dpdklab
2024-08-13 19:00 ` |SUCCESS| " dpdklab
2024-08-13 19:01 ` |PENDING| " dpdklab
2024-08-13 19:02 ` dpdklab
2024-08-13 19:03 ` dpdklab
2024-08-13 19:03 ` dpdklab
2024-08-13 19:03 ` dpdklab
2024-08-13 19:03 ` dpdklab
2024-08-13 19:03 ` |SUCCESS| " dpdklab
2024-08-13 19:03 ` |PENDING| " dpdklab
2024-08-13 19:04 ` dpdklab
2024-08-13 19:04 ` dpdklab
2024-08-13 19:06 ` dpdklab
2024-08-13 19:06 ` dpdklab
2024-08-13 19:08 ` dpdklab
2024-08-13 19:08 ` dpdklab
2024-08-13 19:08 ` dpdklab
2024-08-13 19:08 ` dpdklab
2024-08-13 19:08 ` dpdklab
2024-08-13 19:08 ` dpdklab
2024-08-13 19:10 ` dpdklab
2024-08-13 19:10 ` dpdklab
2024-08-13 19:10 ` dpdklab
2024-08-13 19:11 ` dpdklab
2024-08-13 19:13 ` dpdklab
2024-08-13 19:14 ` dpdklab
2024-08-13 19:14 ` dpdklab
2024-08-13 19:15 ` dpdklab
2024-08-13 19:16 ` dpdklab
2024-08-13 19:17 ` dpdklab
2024-08-13 19:17 ` dpdklab
2024-08-13 19:18 ` dpdklab
2024-08-13 19:19 ` dpdklab
2024-08-13 19:19 ` dpdklab
2024-08-13 19:21 ` |SUCCESS| " dpdklab
2024-08-13 19:21 ` |PENDING| " dpdklab
2024-08-13 19:24 ` dpdklab
2024-08-13 19:24 ` dpdklab
2024-08-13 19:24 ` dpdklab
2024-08-13 19:24 ` dpdklab
2024-08-13 19:25 ` dpdklab
2024-08-13 19:26 ` |SUCCESS| " dpdklab
2024-08-13 19:26 ` |PENDING| " dpdklab
2024-08-13 19:27 ` |SUCCESS| " dpdklab
2024-08-13 19:27 ` dpdklab
2024-08-13 19:28 ` dpdklab
2024-08-13 19:31 ` dpdklab
2024-08-13 19:31 ` |PENDING| " dpdklab
2024-08-13 19:33 ` |SUCCESS| " dpdklab
2024-08-13 19:37 ` |PENDING| " dpdklab
2024-08-13 19:38 ` dpdklab
2024-08-13 19:39 ` dpdklab
2024-08-13 19:40 ` dpdklab
2024-08-13 19:43 ` dpdklab
2024-08-13 19:45 ` |SUCCESS| " dpdklab
2024-08-13 19:52 ` dpdklab
2024-08-13 20:02 ` |PENDING| " dpdklab
2024-08-13 20:04 ` |SUCCESS| " dpdklab
2024-08-13 20:13 ` |PENDING| " dpdklab
2024-08-13 20:14 ` |SUCCESS| " 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=20240813170234.3855030-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).