On 2023/11/26 8:44 PM, Luca Boccassi wrote:
On Sun, 26 Nov 2023 at 01:55, Ruifeng Wang <ruifeng.w...@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
