autotest: disable lcores_autotest on ppc
PATCH 1/1 autotest: disable lcores_autotest on ppc
From: Luca Boccassi <[email protected]>
This test consistently times out on ppc64 builds. Disable it.
---
It just times out, nothing useful in the verbose logs. Eg:
https://ci.debian.net/data/autopkgtest/unstable/ppc64el/d/dpdk/11755163/log.gz
app/test/meson.build | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
app/test/meson.build +5 -1
@@ -215,7 +215,6 @@ fast_tests = [ ['hash_autotest', true], ['interrupt_autotest', true], ['ipfrag_autotest', false], - ['lcores_autotest', true], ['logs_autotest', true], ['lpm_autotest', true], ['lpm6_autotest', true],
@@ -422,6 +421,11 @@ if dpdk_conf.has('RTE_CRYPTO_SCHEDULER') test_deps += 'crypto_scheduler' endif +# This test consistently times out on ppc64 +if arch_subdir != 'ppc' + fast_tests += [['lcores_autotest', true]] +endif + foreach d:test_deps def_lib = get_option('default_library') test_dep_objs += get_variable(def_lib + '_rte_' + d)
Signature · 1 line
2.29.2
20/04/2021 13:45, [email protected]:
Quoted 1 line
This test consistently times out on ppc64 builds. Disable it.
It looks like hiding an issue.
Is there any specific reason for this timeout?
Quoted 5 lines · Thomas Monjalon
20/04/2021 13:45, [email protected]:
Quoted 1 line
This test consistently times out on ppc64 builds. Disable it.
It looks like hiding an issue.
Is there any specific reason for this timeout?
As mentioned in the message, there's nothing useful in the logs, it just times out.
Signature · 2 lines
Kind regards, Luca Boccassi
22/04/2021 12:26, Luca Boccassi:
Quoted 9 lines · Thomas Monjalon
Quoted 5 lines
20/04/2021 13:45, [email protected]:
Quoted 1 line
This test consistently times out on ppc64 builds. Disable it.
It looks like hiding an issue.
Is there any specific reason for this timeout?As mentioned in the message, there's nothing useful in the logs, it just times out.
OK but it could be fixed probably instead of disabling.
Quoted 5 lines · Thomas Monjalon
22/04/2021 12:26, Luca Boccassi:
Quoted 4 lines · Thomas Monjalon
Quoted 3 lines
20/04/2021 13:45, [email protected]:
Quoted 1 line
This test consistently times out on ppc64 builds. Disable it.
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
It looks like hiding an issue.
Is there any specific reason for this timeout?As mentioned in the message, there's nothing useful in the logs, it just times out.
OK but it could be fixed probably instead of disabling.
I'm sure it could, and it would be great if somebody would do so - but
I do not have either the time or the hardware to take care of PPC-specific problems, apart from the bare minimum to remove blockers to get things done for Debian 11.
Signature · 2 lines
Kind regards, Luca Boccassi
22/04/2021 14:36, Luca Boccassi:
Quoted 12 lines · Thomas Monjalon
Quoted 11 lines
22/04/2021 12:26, Luca Boccassi:
Quoted 9 lines · Thomas Monjalon
Quoted 5 lines
20/04/2021 13:45, [email protected]:
Quoted 1 line
This test consistently times out on ppc64 builds. Disable it.
It looks like hiding an issue.
Is there any specific reason for this timeout?As mentioned in the message, there's nothing useful in the logs, it just times out.
Quoted 6 lines
Quoted 1 line
OK but it could be fixed probably instead of disabling.
I'm sure it could, and it would be great if somebody would do so - but I do not have either the time or the hardware to take care of PPC-specific problems, apart from the bare minimum to remove blockers to get things done for Debian 11.
First things first, let's Cc the PPC maintainer:
David Christensen <[email protected]>
Quoted 15 lines · Thomas Monjalon
22/04/2021 14:36, Luca Boccassi:
Quoted 14 lines · Thomas Monjalon
Quoted 12 lines
22/04/2021 12:26, Luca Boccassi:
Quoted 9 lines · Thomas Monjalon
Quoted 5 lines
20/04/2021 13:45, [email protected]:
Quoted 1 line
This test consistently times out on ppc64 builds. Disable it.
It looks like hiding an issue.
Is there any specific reason for this timeout?As mentioned in the message, there's nothing useful in the logs, it just times out.
OK but it could be fixed probably instead of disabling.
Quoted 7 lines
Quoted 4 lines
I'm sure it could, and it would be great if somebody would do so - but I do not have either the time or the hardware to take care of PPC-specific problems, apart from the bare minimum to remove blockers to get things done for Debian 11.
First things first, let's Cc the PPC maintainer:
David Christensen <[email protected]>
https://bugs.dpdk.org/show_bug.cgi?id=684
Signature · 2 lines
Kind regards, Luca Boccassi
Quoted 4 lines
Quoted 2 lines
First things first, let's Cc the PPC maintainer:
David Christensen <[email protected]>
Tried GCC 10 on RHEL 8.3 and running the lcores_autotest individually does not produce any errors. I can't see in the log file how the test is called when it generates an error. Can anyone point out the parameters required to run the test in the situation?
Dave
Quoted 7 lines · On 4/20/21 4:45 AM, [email protected] wrote:
From: Luca Boccassi <[email protected]>
This test consistently times out on ppc64 builds. Disable it.
Signed-off-by Luca Boccassi <[email protected]>
Is there something new about how/when this test is run during continuous integration? The test time is dependent on the value of RTE_MAX_LCORE which is currently 1536. When I run the test locally it takes around 50 seconds to complete and completes without errors. If I reduce the value down to 128 the test completes in around 5 seconds. The current value has been in the code for nearly 2 years so I'm curious why the sudden change in CI results.
We could could reduce the default value for RTE_MAX_LCORE (I don't often have access to a system that actually has this many cores) or we could skip the test in this situation as well.
Dave
Quoted 8 lines · On 4/20/21 4:45 AM, [email protected] wrote:
From: Luca Boccassi <[email protected]>
This test consistently times out on ppc64 builds. Disable it.
Signed-off-by Luca Boccassi <[email protected]>---
NAK. Will resolve with a different patch to reduce the max_lcore value used for PPC builds. Both x86 and PPC require > 30 seconds if the max_lcore value is set to 1536.
Dave