The cgroup selftests lack a settings file, causing the kselftest runner to apply its default 45s timeout. The test_cpu binary now exceeds this limit, resulting in timeout failures that prevent the final test cases from reporting results:
not ok 2 selftests: cgroup: test_cpu # TIMEOUT 45 seconds Test execution times: |Test | Duration | |----------------------|-------------------- | |cpu.weight (×4) | ~10s each | |test_cpucg_stats | 2s CPU time | |test_cpucg_nice | 2s CPU time | |test_cpucg_max | 1000/HZ seconds | |test_cpucg_max_nested | 1000/HZ seconds | Total runtime: ~46s at HZ=1000, ~64s at HZ=100 When executed independently, all nine test cases complete successfully (46.2s on a ppc64le HZ=1000 guest). Introduce a settings file that increases the timeout to 120 seconds, providing sufficient margin above the HZ=100 worst-case scenario. Signed-off-by: Vishal Chourasia <[email protected]> --- tools/testing/selftests/cgroup/settings | 1 + 1 file changed, 1 insertion(+) create mode 100644 tools/testing/selftests/cgroup/settings diff --git a/tools/testing/selftests/cgroup/settings b/tools/testing/selftests/cgroup/settings new file mode 100644 index 000000000000..6091b45d226b --- /dev/null +++ b/tools/testing/selftests/cgroup/settings @@ -0,0 +1 @@ +timeout=120 -- 2.54.0
