summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorVishal Chourasia <vishalc@linux.ibm.com>2026-09-29 01:30:34 +0530
committerTejun Heo <tj@kernel.org>2026-09-28 10:14:13 -1000
commita6d4aee572e81144d6f0867a9c1af3020869d406 (patch)
tree70bad89b657ab01069aae13fd3ff03d61119d994 /tools/perf/scripts/python
parent85ad3963de964ed58e43b2ea7b6dea8b9a22adb3 (diff)
downloadlinux-next-a6d4aee572e81144d6f0867a9c1af3020869d406.tar.gz
linux-next-a6d4aee572e81144d6f0867a9c1af3020869d406.zip
selftests/cgroup: add settings file with a longer timeout
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 <vishalc@linux.ibm.com> Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions