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| pw139476 [PATCH 16/16] build: enable vla warnings on Windows built code
Date: Wed, 17 Apr 2024 20:44:56 -0400	[thread overview]
Message-ID: <20240418004456.2443850-1-robot@bytheb.org> (raw)
In-Reply-To: <1713397319-26135-17-git-send-email-roretzla@linux.microsoft.com>

From: robot@bytheb.org

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

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

  parent reply	other threads:[~2024-04-18  0:45 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1713397319-26135-17-git-send-email-roretzla@linux.microsoft.com>
2024-04-17 23:21 ` |SUCCESS| pw139462-139476 " qemudev
2024-04-17 23:25 ` qemudev
2024-04-17 23:44 ` |SUCCESS| pw139476 " checkpatch
2024-04-18  0:41 ` |SUCCESS| pw139462-139476 [PATCH] [16/16] build: enable vla warnings dpdklab
2024-04-18  0:41 ` dpdklab
2024-04-18  0:42 ` dpdklab
2024-04-18  0:42 ` dpdklab
2024-04-18  0:44 ` 0-day Robot [this message]
2024-04-18  0:49 ` dpdklab
2024-04-18  0:50 ` dpdklab
2024-04-18  0:51 ` dpdklab
2024-04-18  0:51 ` dpdklab
2024-04-18  0:52 ` dpdklab
2024-04-18  0:52 ` dpdklab
2024-04-18  0:53 ` dpdklab
2024-04-18  0:53 ` dpdklab
2024-04-18  0:53 ` dpdklab
2024-04-18  0:54 ` dpdklab
2024-04-18  0:54 ` dpdklab
2024-04-18  0:55 ` dpdklab
2024-04-18  0:57 ` dpdklab
2024-04-18  0:57 ` dpdklab
2024-04-18  0:57 ` dpdklab
2024-04-18  0:58 ` dpdklab
2024-04-18  1:02 ` dpdklab
2024-04-18  1:04 ` dpdklab
2024-04-18  1:04 ` dpdklab
2024-04-18  1:04 ` dpdklab
2024-04-18  1:09 ` dpdklab
2024-04-18  1:10 ` dpdklab
2024-04-18  1:11 ` dpdklab
2024-04-18  1:11 ` dpdklab
2024-04-18  1:12 ` dpdklab
2024-04-18  1:12 ` dpdklab
2024-04-18  1:12 ` dpdklab
2024-04-18  1:13 ` dpdklab
2024-04-18  1:13 ` dpdklab
2024-04-18  1:14 ` dpdklab
2024-04-18  1:14 ` dpdklab
2024-04-18  1:14 ` dpdklab
2024-04-18  1:17 ` dpdklab
2024-04-18  1:17 ` dpdklab
2024-04-18  1:26 ` dpdklab
2024-04-18  1:28 ` dpdklab
2024-04-18  1:30 ` dpdklab
2024-04-18  1:30 ` dpdklab
2024-04-18  1:31 ` dpdklab
2024-04-18  1:31 ` dpdklab
2024-04-18  1:31 ` dpdklab
2024-04-18  1:32 ` dpdklab
2024-04-18  1:32 ` dpdklab
2024-04-18  1:33 ` dpdklab
2024-04-18  1:33 ` dpdklab
2024-04-18  1:36 ` dpdklab
2024-04-18  1:37 ` dpdklab
2024-04-18  1:37 ` dpdklab
2024-04-18  1:37 ` dpdklab
2024-04-18  1:37 ` dpdklab
2024-04-18  1:38 ` dpdklab
2024-04-18  1:38 ` dpdklab
2024-04-18  1:38 ` dpdklab
2024-04-18  1:38 ` dpdklab
2024-04-18  1:39 ` dpdklab
2024-04-18  1:40 ` dpdklab
2024-04-18  1:40 ` dpdklab
2024-04-18  1:40 ` dpdklab
2024-04-18  1:40 ` dpdklab
2024-04-18  1:41 ` dpdklab
2024-04-18  1:41 ` dpdklab
2024-04-18  1:41 ` dpdklab
2024-04-18  1:42 ` dpdklab
2024-04-18  1:52 ` dpdklab
2024-04-18  1:54 ` dpdklab
2024-04-18  1:55 ` dpdklab
2024-04-18  1:56 ` dpdklab
2024-04-18  1:57 ` dpdklab
2024-04-18  1:57 ` dpdklab
2024-04-18  1:58 ` dpdklab
2024-04-18  2:00 ` dpdklab
2024-04-18  2:25 ` dpdklab
2024-04-18  2:26 ` dpdklab
2024-04-18  2:32 ` dpdklab
2024-04-18  2:34 ` dpdklab
2024-04-18  2:37 ` dpdklab
2024-04-18  2:42 ` dpdklab
2024-04-18  2:46 ` dpdklab
2024-04-18  2:50 ` dpdklab
2024-04-18  2:53 ` dpdklab
2024-04-18  2:54 ` dpdklab
2024-04-18  2:56 ` dpdklab
2024-04-18  3:35 ` dpdklab
2024-04-18  4:11 ` dpdklab
2024-04-18  4:26 ` 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=20240418004456.2443850-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).