<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux-next.git/tools/testing/selftests/cgroup/settings, branch master</title>
<subtitle>Linux kernel latest source</subtitle>
<id>http://mirrors.hust.edu.cn/git/linux-next.git/atom?h=master</id>
<link rel='self' href='http://mirrors.hust.edu.cn/git/linux-next.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/linux-next.git/'/>
<updated>2026-09-28T20:14:13+00:00</updated>
<entry>
<title>selftests/cgroup: add settings file with a longer timeout</title>
<updated>2026-09-28T20:14:13+00:00</updated>
<author>
<name>Vishal Chourasia</name>
<email>vishalc@linux.ibm.com</email>
</author>
<published>2026-09-28T20:00:34+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/linux-next.git/commit/?id=a6d4aee572e81144d6f0867a9c1af3020869d406'/>
<id>urn:sha1:a6d4aee572e81144d6f0867a9c1af3020869d406</id>
<content type='text'>
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 &lt;vishalc@linux.ibm.com&gt;
Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
</content>
</entry>
</feed>
