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| pw153791 [PATCH v3 10/10] net/ice/base: update version info
Date: Tue, 27 May 2025 10:45:19 -0400	[thread overview]
Message-ID: <20250527144519.3596155-1-robot@bytheb.org> (raw)
In-Reply-To: <20250527131741.7606-11-dhanya.r.pillai@intel.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2025-05-27 14:45 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250527131741.7606-11-dhanya.r.pillai@intel.com>
2025-05-27 12:45 ` |SUCCESS| pw153782-153791 " qemudev
2025-05-27 12:50 ` qemudev
2025-05-27 13:20 ` |SUCCESS| pw153791 " checkpatch
2025-05-27 14:45 ` 0-day Robot [this message]
2025-05-28  5:15 ` |SUCCESS| pw153782-153791 [PATCH] [v3,10/10] net/ice/base: update ve dpdklab
2025-05-28  5:17 ` dpdklab
2025-05-28  5:24 ` dpdklab
2025-05-28  5:53 ` dpdklab
2025-05-28  5:59 ` dpdklab
2025-05-28  6:36 ` dpdklab
2025-05-28  6:37 ` dpdklab
2025-05-28  6:53 ` dpdklab
2025-05-28  7:22 ` |PENDING| " dpdklab
2025-05-28  7:27 ` dpdklab
2025-05-28  7:27 ` |SUCCESS| " dpdklab
2025-05-28  7:48 ` dpdklab
2025-05-28  7:48 ` dpdklab
2025-05-28  8:08 ` dpdklab
2025-05-28  8:25 ` dpdklab
2025-05-28  8:41 ` dpdklab
2025-05-28  8:42 ` dpdklab
2025-05-28  8:59 ` dpdklab
2025-05-28  9:43 ` |PENDING| " dpdklab
2025-05-28  9:52 ` |SUCCESS| " dpdklab
2025-05-28 10:36 ` |WARNING| " dpdklab
2025-05-28 10:38 ` |SUCCESS| " dpdklab
2025-05-28 11:21 ` dpdklab
2025-05-28 11:39 ` |WARNING| " dpdklab
2025-05-28 13:07 ` |PENDING| " dpdklab
2025-05-28 13:07 ` dpdklab
2025-05-28 13:35 ` |SUCCESS| " dpdklab
2025-05-28 14:10 ` dpdklab
2025-05-28 14:11 ` dpdklab
2025-05-28 14:11 ` |PENDING| " dpdklab
2025-05-28 14:21 ` |SUCCESS| " dpdklab
2025-05-28 14:26 ` |PENDING| " dpdklab
2025-05-28 14:50 ` |WARNING| " dpdklab
2025-05-28 14:51 ` dpdklab
2025-05-28 15:00 ` |SUCCESS| " dpdklab
2025-05-28 15:12 ` |WARNING| " dpdklab
2025-05-28 16:28 ` dpdklab
2025-05-28 16:33 ` |SUCCESS| " dpdklab
2025-05-28 17:08 ` dpdklab
2025-05-28 17:09 ` dpdklab
2025-05-28 17:31 ` dpdklab
2025-05-28 20:14 ` |WARNING| " dpdklab
2025-05-28 22:59 ` |SUCCESS| " dpdklab
2025-05-28 23:56 ` dpdklab
2025-05-29  0:37 ` dpdklab
2025-05-29  1:59 ` |WARNING| " dpdklab
2025-05-29  2:58 ` dpdklab
2025-05-29 12:16 ` |SUCCESS| " dpdklab
2025-05-29 14:19 ` dpdklab
2025-05-29 16:14 ` |WARNING| " dpdklab
2025-05-29 17:51 ` dpdklab
2025-06-03 20:34 ` |SUCCESS| " dpdklab
2025-06-03 20:39 ` dpdklab
2025-06-04  5:20 ` dpdklab
2025-06-04  6:11 ` 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=20250527144519.3596155-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).