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| pw142725 [RFC PATCH v1 1/1] devtools: add vscode configuration generator
Date: Fri, 26 Jul 2024 09:44:10 -0400	[thread overview]
Message-ID: <20240726134410.765971-1-robot@bytheb.org> (raw)
In-Reply-To: <6a6b20c037cffcc5f68a341c4b4e4f21990ae991.1721997016.git.anatoly.burakov@intel.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-07-26 13:44 UTC|newest]

Thread overview: 97+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6a6b20c037cffcc5f68a341c4b4e4f21990ae991.1721997016.git.anatoly.burakov@intel.com>
2024-07-26 12:17 ` qemudev
2024-07-26 12:21 ` qemudev
2024-07-26 12:44 ` checkpatch
2024-07-26 13:44 ` 0-day Robot [this message]
2024-07-26 22:56 ` |SUCCESS| pw142725 [PATCH] [RFC,v1,1/1] devtools: add vscode configu dpdklab
2024-07-27  0:22 ` |PENDING| " dpdklab
2024-07-27  0:32 ` dpdklab
2024-07-27  0:59 ` dpdklab
2024-07-27  1:02 ` dpdklab
2024-07-27  1:04 ` dpdklab
2024-07-27  1:06 ` dpdklab
2024-07-27  1:06 ` dpdklab
2024-07-27  1:07 ` dpdklab
2024-07-27  1:10 ` |SUCCESS| " dpdklab
2024-07-27  1:12 ` |PENDING| " dpdklab
2024-07-27  1:13 ` |SUCCESS| " dpdklab
2024-07-27  1:21 ` |PENDING| " dpdklab
2024-07-27  1:27 ` dpdklab
2024-07-27  1:29 ` dpdklab
2024-07-27  1:33 ` dpdklab
2024-07-27  1:33 ` dpdklab
2024-07-27  1:34 ` dpdklab
2024-07-27  1:35 ` dpdklab
2024-07-27  1:37 ` dpdklab
2024-07-27  1:37 ` dpdklab
2024-07-27  1:38 ` dpdklab
2024-07-27  1:38 ` dpdklab
2024-07-27  1:38 ` dpdklab
2024-07-27  1:39 ` dpdklab
2024-07-27  1:40 ` dpdklab
2024-07-27  1:42 ` dpdklab
2024-07-27  1:43 ` dpdklab
2024-07-27  1:43 ` dpdklab
2024-07-27  1:43 ` dpdklab
2024-07-27  1:44 ` dpdklab
2024-07-27  1:44 ` dpdklab
2024-07-27  1:45 ` dpdklab
2024-07-27  1:45 ` |SUCCESS| " dpdklab
2024-07-27  1:45 ` |PENDING| " dpdklab
2024-07-27  1:46 ` dpdklab
2024-07-27  1:46 ` dpdklab
2024-07-27  1:47 ` dpdklab
2024-07-27  1:47 ` dpdklab
2024-07-27  1:48 ` dpdklab
2024-07-27  1:48 ` dpdklab
2024-07-27  1:49 ` dpdklab
2024-07-27  1:49 ` dpdklab
2024-07-27  1:49 ` dpdklab
2024-07-27  1:49 ` dpdklab
2024-07-27  1:50 ` dpdklab
2024-07-27  1:51 ` dpdklab
2024-07-27  1:52 ` dpdklab
2024-07-27  1:54 ` dpdklab
2024-07-27  1:57 ` dpdklab
2024-07-27  1:57 ` dpdklab
2024-07-27  1:58 ` dpdklab
2024-07-27  1:58 ` dpdklab
2024-07-27  1:59 ` dpdklab
2024-07-27  1:59 ` dpdklab
2024-07-27  2:00 ` dpdklab
2024-07-27  2:02 ` dpdklab
2024-07-27  2:03 ` dpdklab
2024-07-27  2:04 ` dpdklab
2024-07-27  2:06 ` dpdklab
2024-07-27  2:06 ` |SUCCESS| " dpdklab
2024-07-27  2:07 ` |PENDING| " dpdklab
2024-07-27  2:08 ` dpdklab
2024-07-27  2:08 ` dpdklab
2024-07-27  2:08 ` dpdklab
2024-07-27  2:11 ` dpdklab
2024-07-27  2:12 ` dpdklab
2024-07-27  2:12 ` dpdklab
2024-07-27  2:14 ` dpdklab
2024-07-27  2:17 ` dpdklab
2024-07-27  2:18 ` dpdklab
2024-07-27  2:19 ` |SUCCESS| " dpdklab
2024-07-27  2:19 ` |PENDING| " dpdklab
2024-07-27  2:23 ` dpdklab
2024-07-27  2:23 ` dpdklab
2024-07-27  2:25 ` dpdklab
2024-07-27  2:27 ` dpdklab
2024-07-27  2:27 ` dpdklab
2024-07-27  2:27 ` dpdklab
2024-07-27  2:28 ` dpdklab
2024-07-27  2:29 ` dpdklab
2024-07-27  2:33 ` dpdklab
2024-07-27  2:35 ` |SUCCESS| " dpdklab
2024-07-27  2:35 ` dpdklab
2024-07-27  2:36 ` |PENDING| " dpdklab
2024-07-27  2:39 ` |SUCCESS| " dpdklab
2024-07-27  2:41 ` dpdklab
2024-07-27  2:43 ` dpdklab
2024-07-27  2:49 ` |PENDING| " dpdklab
2024-07-27  3:03 ` |SUCCESS| " dpdklab
2024-07-27  3:03 ` dpdklab
2024-07-27  3:04 ` dpdklab
2024-07-27  3:53 ` 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=20240726134410.765971-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).