Skip to contentSkip to conversation

selftests/mm: Increase timeout from 180 to 900 seconds

PATCH Applied Shivank Garg 2 participants 3 messages Jun 9, 2025 – Jun 10, 2025

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 selftests/mm: Increase timeout from 180 to 900 seconds

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.

---
 tools/testing/selftests/mm/settings | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
tools/testing/selftests/mm/settings +1 -1
index a953c96aa16e..e2206265f67c 100644
@@ -1 +1 @@
-timeout=180
+timeout=900
Signature · 1 line
2.43.0
maintainer
#1 lore raw
Quoted 12 lines · On Mon, 9 Jun 2025 12:06:07 +0000 Shivank Garg <[email protected]> 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.

...

tools/testing/selftests/mm/settings line 1

Quoted 2 lines
tools/testing/selftests/mm/settings +1 -1
@@ -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.

#2 lore raw
Quoted 19 lines · Andrew Morton
Quoted 12 lines · On Mon, 9 Jun 2025 12:06:07 +0000 Shivank Garg <[email protected]> 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.

...

tools/testing/selftests/mm/settings line 1

Quoted 2 lines
tools/testing/selftests/mm/settings +1 -1
@@ -1 +1 @@
-timeout=180
+timeout=900

Gee, that's a bit crude, isn't it. I have a laptop which will need 90000 ;)

Quoted 3 lines

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