The mm selftests are timing out with the current 180-second limit. Testing shows that run_vmtests.sh takes approximately 11 minutes (664 seconds) to complete.
Increase the timeout to 900 seconds (15 minutes) to provide sufficient buffer for the tests to complete successfully.
Signed-off-by: Shivank Garg shivankg@amd.com --- tools/testing/selftests/mm/settings | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/mm/settings b/tools/testing/selftests/mm/settings index a953c96aa16e..e2206265f67c 100644 --- a/tools/testing/selftests/mm/settings +++ b/tools/testing/selftests/mm/settings @@ -1 +1 @@ -timeout=180 +timeout=900
On Mon, 9 Jun 2025 12:06:07 +0000 Shivank Garg shivankg@amd.com wrote:
The mm selftests are timing out with the current 180-second limit. Testing shows that run_vmtests.sh takes approximately 11 minutes (664 seconds) to complete.
Increase the timeout to 900 seconds (15 minutes) to provide sufficient buffer for the tests to complete successfully.
...
--- a/tools/testing/selftests/mm/settings +++ b/tools/testing/selftests/mm/settings @@ -1 +1 @@ -timeout=180 +timeout=900
Gee, that's a bit crude, isn't it. I have a laptop which will need 90000 ;)
I guess it's better than it was before. Some sort of smarter monitor of ongoing activity can be bothered about later.
On 6/10/2025 4:37 AM, Andrew Morton wrote:
On Mon, 9 Jun 2025 12:06:07 +0000 Shivank Garg shivankg@amd.com wrote:
The mm selftests are timing out with the current 180-second limit. Testing shows that run_vmtests.sh takes approximately 11 minutes (664 seconds) to complete.
Increase the timeout to 900 seconds (15 minutes) to provide sufficient buffer for the tests to complete successfully.
...
--- a/tools/testing/selftests/mm/settings +++ b/tools/testing/selftests/mm/settings @@ -1 +1 @@ -timeout=180 +timeout=900
Gee, that's a bit crude, isn't it. I have a laptop which will need 90000 ;)
I guess it's better than it was before. Some sort of smarter monitor of ongoing activity can be bothered about later.
900s is crude, and I can imagine some systems needing even more time! I think the real issue is run_vmtests.sh bundles many tests together. Most finish quickly but few (e.g. compaction) tests take significant time. I agree that a smarter approach with per-test timeouts would be better.
Thanks, Shivank
linux-kselftest-mirror@lists.linaro.org