DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Marat Khalili <marat.khalili@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v2 01/10] app/test: make parameters clearer when adding fast tests
Date: Fri, 5 Dec 2025 10:17:32 +0000	[thread overview]
Message-ID: <aTKxPLHEREaH5Gqk@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <5b0438bc0a494ca5972718b7f9e1ce22@huawei.com>

On Fri, Dec 05, 2025 at 10:10:34AM +0000, Marat Khalili wrote:
> Apart from one cosmetic issue in a comment,
> 
> Acked-by: Marat Khalili <marat.khalili@huawei.com>
> 
> > diff --git a/app/test/suites/meson.build b/app/test/suites/meson.build
> > index 712dd65568..65995078b7 100644
> > --- a/app/test/suites/meson.build
> > +++ b/app/test/suites/meson.build
> > @@ -67,9 +67,19 @@ foreach suite:test_suites
> >          # special fast-test handling here
> >          foreach t: suite_tests
> >              params = t.split(':')
> > +            # check for valid options for asan and nohuge. Note, the extraction script runs tolower()
> 
> > diff --git a/buildtools/get-test-suites.py b/buildtools/get-test-suites.py
> > index c3a99a862e..73f1d9c9e1 100644
> > --- a/buildtools/get-test-suites.py
> > +++ b/buildtools/get-test-suites.py
> > @@ -18,7 +18,7 @@ def get_fast_test_params(test_name, ln):
> >      "Extract the extra fast-test parameters from the line"
> >      (_, rest_of_line) = ln.split(test_name, 1)
> >      (_, nohuge, asan, _func) = rest_of_line.split(',', 3)
> > -    return f":{nohuge.strip().lower()}:{asan.strip().lower()}"
> > +    return f":{nohuge.strip()}:{asan.strip()}"
> 
> Is the Note above no longer relevant?
> 
Ooops, yes, good catch.


  reply	other threads:[~2025-12-05 10:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 15:49 [PATCH 0/2] improve fast-tests suite Bruce Richardson
2025-12-02 15:49 ` [PATCH 1/2] app/test: add some unattached tests to fast-test suite Bruce Richardson
2025-12-02 15:49 ` [PATCH 2/2] app/test: make parameters clearer when adding fast tests Bruce Richardson
2025-12-02 16:53   ` Marat Khalili
2025-12-02 18:16     ` Bruce Richardson
2025-12-04 18:20 ` [PATCH v2 00/10] Assign all unit tests to suites Bruce Richardson
2025-12-04 18:20   ` [PATCH v2 01/10] app/test: make parameters clearer when adding fast tests Bruce Richardson
2025-12-05 10:10     ` Marat Khalili
2025-12-05 10:17       ` Bruce Richardson [this message]
2025-12-04 18:20   ` [PATCH v2 02/10] app/test: fix undefined behaviour in red autotest Bruce Richardson
2025-12-05 10:25     ` Marat Khalili
2025-12-04 18:20   ` [PATCH v2 03/10] app/test: reduce duration of secondary timer test Bruce Richardson
2025-12-04 18:20   ` [PATCH v2 04/10] app/test: fix timer loop hang on secondary process failure Bruce Richardson
2025-12-04 18:20   ` [PATCH v2 05/10] eal: add internal APIs to query loaded driver paths Bruce Richardson
2025-12-04 18:20   ` [PATCH v2 06/10] app/test: pass loaded driver info to secondary procs Bruce Richardson
2025-12-04 18:20   ` [PATCH v2 07/10] app/test: skip power capabilities test if unsupported Bruce Richardson
2025-12-04 18:20   ` [PATCH v2 08/10] app/test: add some unattached tests to fast-test suite Bruce Richardson
2025-12-05 12:37     ` David Marchand
2025-12-05 12:43       ` Bruce Richardson
2025-12-05 12:50         ` David Marchand
2025-12-05 12:53           ` Bruce Richardson
2025-12-05 13:08             ` David Marchand
2025-12-04 18:20   ` [PATCH v2 09/10] app/test: add tests to driver test suite Bruce Richardson
2025-12-04 18:20   ` [PATCH v2 10/10] buildtools/get-test-suites: suppress empty output Bruce Richardson
2025-12-05 10:29     ` Marat Khalili

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=aTKxPLHEREaH5Gqk@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=marat.khalili@huawei.com \
    /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).