DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: Re: [PATCH 3/4] test: make red test part of fast suite
Date: Tue, 6 Aug 2024 14:28:13 +0200	[thread overview]
Message-ID: <CAJFAV8xvsa97Zi5Rc8M2BRKz7MDKb_DEM3q4UnnFduYBW77gEA@mail.gmail.com> (raw)
In-Reply-To: <20240718191049.84865-4-stephen@networkplumber.org>

On Thu, Jul 18, 2024 at 9:11 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> The red tests were not run because not part of any suite.
> Meson warning is:
>  WARNING: Test "red_autotest" is not defined in any test suite
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>

There is an open bz about this unit test.
https://bugs.dpdk.org/show_bug.cgi?id=826


-- 
David Marchand


  parent reply	other threads:[~2024-08-06 12:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 19:07 [PATCH 0/4] Enable more unit tests Stephen Hemminger
2024-07-18 19:07 ` [PATCH 1/4] test: update alarm test Stephen Hemminger
2024-07-19 10:17   ` Bruce Richardson
2024-07-19 17:09     ` Stephen Hemminger
2024-08-06 12:45   ` David Marchand
2024-08-07 22:24     ` Stephen Hemminger
2024-08-08 18:52     ` Stephen Hemminger
2024-07-18 19:07 ` [PATCH 2/4] test: run cksum tests as part of perf test suite Stephen Hemminger
2024-07-19  8:45   ` Bruce Richardson
2024-07-18 19:07 ` [PATCH 3/4] test: make red test part of fast suite Stephen Hemminger
2024-07-19  9:14   ` Bruce Richardson
2024-08-06 12:28   ` David Marchand [this message]
2024-08-06 12:49     ` Bruce Richardson
2024-08-08 16:12     ` Stephen Hemminger
2024-10-04 12:17       ` David Marchand
2024-07-18 19:07 ` [PATCH 4/4] test: run timer secondary tests as " Stephen Hemminger
2024-07-19  9:27   ` Bruce Richardson
2024-10-04 12:20   ` David Marchand
2024-10-04 12:51 ` [PATCH 0/4] Enable more unit tests David Marchand

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=CAJFAV8xvsa97Zi5Rc8M2BRKz7MDKb_DEM3q4UnnFduYBW77gEA@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).