From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Luca Boccassi <bluca@debian.org>,
Ruifeng Wang <Ruifeng.Wang@arm.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Marchand, David" <david.marchand@redhat.com>,
nd@arm.com
Subject: Re: DPDK Release Status Meeting 2023-11-23
Date: Mon, 27 Nov 2023 09:16:30 -0800 [thread overview]
Message-ID: <20231127091630.2b83425c@hermes.local> (raw)
In-Reply-To: <5519528.NG923GbCHz@thomas>
On Mon, 27 Nov 2023 11:13:16 +0100
Thomas Monjalon <thomas@monjalon.net> wrote:
> ish.
> > >>
> > >> Due to a relative bigger RTE_MAX_LCORE value on ARM, the unit test case
> > >> would take a longer time to finish iterations.
> > >> In one of my run, the case took about 100s.
> > >
> > > Right, but this test is part of the "fast suite", and more than a
> > > minute is not exactly fast. So one of the following should ideally
> > > happen:
> >
> > Agree.
> >
> > > 1) Test is moved out of the fast suite
> > > 2) Test has its individual timeout sized appropriately so that it
> > > never fails regardless of the environment
> > > 3) Test is capped so that it doesn't grow with the number of cores
> > > without limits
> >
> > I'm for option 3. The case should be kept in fast suite. Time taken
> > should be capped.
>
> More than 1 second is a bit slow.
> Please make the test really faster.
What is the test trying to exercise? Can it be done in another way?
next prev parent reply other threads:[~2023-11-27 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 8:53 Mcnamara, John
2023-11-26 1:55 ` Ruifeng Wang
2023-11-26 12:44 ` Luca Boccassi
2023-11-27 2:51 ` Ruifeng Wang
2023-11-27 10:13 ` Thomas Monjalon
2023-11-27 17:16 ` Stephen Hemminger [this message]
2023-11-28 5:53 ` Ruifeng Wang
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=20231127091630.2b83425c@hermes.local \
--to=stephen@networkplumber.org \
--cc=Ruifeng.Wang@arm.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=nd@arm.com \
--cc=thomas@monjalon.net \
/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).