From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Luca Boccassi <bluca@debian.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Marchand, David" <david.marchand@redhat.com>,
nd@arm.com
Subject: Re: DPDK Release Status Meeting 2023-11-23
Date: Mon, 27 Nov 2023 10:51:08 +0800 [thread overview]
Message-ID: <2542e606-b66c-4dfb-b363-b885b9e3bfa2@arm.com> (raw)
In-Reply-To: <CAMw=ZnRmEuygVtcy+TJ_vwJt_5ZT8wNUJmF2u1bapAy6d_294w@mail.gmail.com>
On 2023/11/26 8:44 PM, Luca Boccassi wrote:
> On Sun, 26 Nov 2023 at 01:55, Ruifeng Wang <Ruifeng.Wang@arm.com> wrote:
>>
>>
>>
>> On 2023/11/24 4:53 PM, Mcnamara, John wrote:
>>> Release status meeting minutes 2023-11-23
>>>
>> <snip>
>>> issues:
>>>
>>> * Build/link issue on Debian
>>>
>>> https://salsa.debian.org/debian/dpdk/-/jobs/4949787
>>>
>>> * cpfl compilation issue
>>>
>>>
>>> https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/Debian_Next/i586
>>>
>>> * LCOREs autotest timing out on ARM:
>>>
>>>
>>> https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/Debian_12/aarch64
>>
>> The failure relates to test environment. 50s is not enough for lcores
>> test to finish.
>>
>> 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.
Thanks,
Ruifeng
next prev parent reply other threads:[~2023-11-27 2:51 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 [this message]
2023-11-27 10:13 ` Thomas Monjalon
2023-11-27 17:16 ` Stephen Hemminger
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=2542e606-b66c-4dfb-b363-b885b9e3bfa2@arm.com \
--to=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).